8000 doc: add transaction processing chapter with internals info · postgres/postgres@80e5916 · GitHub
[go: up one dir, main page]
Skip to content

Commit 80e5916

Browse files
bmomjianbmomjian
committed
doc: add transaction processing chapter with internals info
This also adds references to this new chapter at relevant sections of our documentation. Previously much of these internal details were exposed to users, but not explained. This also updates RELEASE SAVEPOINT. Discussion: https://postgr.es/m/CANbhV-E_iy9fmrErxrCh8TZTyenpfo72Hf_XD2HLDppva4dUNA@mail.gmail.com Author: Simon Riggs, Laurenz Albe Reviewed-by: Bruce Momjian Backpatch-through: 11
1 parent a282d5f commit 80e5916

File tree

10 files changed

+262
-32
lines changed

10 files changed

+262
-32
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9097,16 +9097,17 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
90979097
<entry></entry>
90989098
<entry>
90999099
Virtual ID of the transaction targeted by the lock,
9100-
or null if the target is not a virtual transaction ID
9100+
or null if the target is not a virtual transaction ID; see
9101+
<xref linkend="transactions"/>
91019102
</entry>
91029103
</row>
91039104
<row>
91049105
<entry><structfield>transactionid</structfield></entry>
91059106
<entry><type>xid</type></entry>
91069107
<entry></entry>
91079108
<entry>
9108-
ID of the transaction targeted by the lock,
9109-
or null if the target is not a transaction ID
9109+
ID of the transaction targeted by the lock, or null if the target
9110+
is not a transaction ID; <xref linkend="transactions"/>
91109111
</entry>
91119112
</row>
91129113
<row>

‎doc/src/sgml/config.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5730,12 +5730,14 @@ local0.* /var/log/postgresql
57305730
</row>
57315731
<row>
57325732
<entry><literal>%v</literal></entry>
5733-
<entry>Virtual transaction ID (backendID/localXID)</entry>
5733+
<entry>Virtual transaction ID (backendID/localXID); see
5734+
<xref linkend="transaction-id"/></entry>
57345735
<entry>no</entry>
57355736
</row>
57365737
<row>
57375738
<entry><literal>%x</literal></entry>
5738-
<entry>Transaction ID (0 if none is assigned)</entry>
5739+
<entry>Transaction ID (0 if none is assigned); see
5740+
<xref linkend="transaction-id"/></entry>
57395741
<entry>no</entry>
57405742
</row>
57415743
<row>

‎doc/src/sgml/filelist.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,7 @@
101101
<!ENTITY protocol SYSTEM "protocol.sgml">
102102
<!ENTITY sources SYSTEM "sources.sgml">
103103
<!ENTITY storage SYSTEM "storage.sgml">
104+
<!ENTITY transaction SYSTEM "xact.sgml">
104105
<!ENTITY tablesample-method SYSTEM "tablesample-method.sgml">
105106
<!ENTITY generic-wal SYSTEM "generic-wal.sgml">
106107

‎doc/src/sgml/monitoring.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -781,7 +781,8 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
781781
<row>
782782
<entry><structfield>backend_xid</structfield></entry>
783783
<entry><type>xid</type></entry>
784-
<entry>Top-level transaction identifier of this backend, if any.</entry>
784+
<entry>Top-level transaction identifier of this backend, if any; see
785+
<xref linkend="transaction-id"/>.</entry>
785786
</row>
786787
<row>
787788
<entry><structfield>backend_xmin</structfield></entry>

‎doc/src/sgml/pgrowlocks.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,8 @@ pgrowlocks(text) returns setof record
5757
<row>
5858
<entry><structfield>locker</structfield></entry>
5959
<entry><type>xid</type></entry>
60-
<entry>Transaction ID of locker, or multixact ID if multitransaction</entry>
60+
<entry>Transaction ID of locker, or multixact ID if
61+
multitransaction; see <xref linkend="transaction-id"/></entry>
6162
</row>
6263
<row>
6364
<entry><structfield>multi</structfield></entry>

‎doc/src/sgml/postgres.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -260,6 +260,7 @@
260260
&brin;
261261
&hash;
262262
&storage;
263+
&transaction;
263264
&bki;
264265
&planstats;
265266

‎doc/src/sgml/ref/release_savepoint.sgml

Lines changed: 41 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ PostgreSQL documentation
2121

2222
<refnamediv>
2323
<refname>RELEASE SAVEPOINT</refname>
24-
<refpurpose>destroy a previously defined savepoint</refpurpose>
24+
<refpurpose>release a previously defined savepoint</refpurpose>
2525
</refnamediv>
2626

2727
<refsynopsisdiv>
@@ -34,23 +34,13 @@ RELEASE [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
3434
<title>Description</title>
3535

3636
<para>
37-
<command>RELEASE SAVEPOINT</command> destroys a savepoint previously defined
38-
in the current transaction.
39-
</para>
40-
41-
<para>
42-
Destroying a savepoint makes it unavailable as a rollback point,
43-
but it has no other user visible behavior. It does not undo the
44-
effects of commands executed after the savepoint was established.
45-
(To do that, see <xref linkend="sql-rollback-to"/>.)
46-
Destroying a savepoint when
47-
it is no longer needed allows the system to reclaim some resources
48-
earlier than transaction end.
49-
</para>
50-
51-
<para>
52-
<command>RELEASE SAVEPOINT</command> also destroys all savepoints that were
53-
established after the named savepoint was established.
37+
<command>RELEASE SAVEPOINT</command> releases the named savepoint and
38+
all active savepoints that were created after the named savepoint,
39+
and frees their resources. All changes made since the creation of
40+
the savepoint that didn't already get rolled back are merged into
41+
the transaction or savepoint that was active when the named savepoint
42+
was created. Changes made after <command>RELEASE SAVEPOINT</command>
43+
will also be part of this active transaction or savepoint.
5444
</para>
5545
</refsect1>
5646

@@ -62,7 +52,7 @@ RELEASE [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
6252
<term><replaceable>savepoint_name</replaceable></term>
6353
<listitem>
6454
<para>
65-
The name of the savepoint to destroy.
55+
The name of the savepoint to release.
6656
</para>
6757
</listitem>
6858
</varlistentry>
@@ -78,7 +68,7 @@ RELEASE [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
7868

7969
<para>
8070
It is not possible to release a savepoint when the transaction is in
81-
an aborted state.
71+
an aborted state; to do that, use <xref linkend="sql-rollback-to"/>.
8272
</para>
8373

8474
<para>
@@ -93,7 +83,7 @@ RELEASE [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
9383
<title>Examples</title>
9484

9585
<para>
96-
To establish and later destroy a savepoint:
86+
To establish and later release a savepoint:
9787
<programlisting>
9888
BEGIN;
9989
INSERT INTO table1 VALUES (3);
@@ -104,6 +94,36 @@ COMMIT;
10494
</programlisting>
10595
The above transaction will insert both 3 and 4.
10696
</para>
97+
98+
<para>
99+
A more complex example with multiple nested subtransactions:
100+
<programlisting>
101+
BEGIN;
102+
INSERT INTO table1 VALUES (1);
103+
SAVEPOINT sp1;
104+
INSERT INTO table1 VALUES (2);
105+
SAVEPOINT sp2;
106+
INSERT INTO table1 VALUES (3);
107+
RELEASE SAVEPOINT sp2;
108+
INSERT INTO table1 VALUES (4))); -- generates an error
109+
</programlisting>
110+
In this example, the application requests the release of the savepoint
111+
<literal>sp2</literal>, which inserted 3. This changes the insert's
112+
transaction context to <literal>sp1</literal>. When the statement
113+
attempting to insert value 4 generates an error, the insertion of 2 and
114+
4 are lost because they are in the same, now-rolled back savepoint,
115+
and value 3 is in the same transaction context. The application can
116+
now only choose one of these two commands, since all other commands
117+
will be ignored:
118+
<programlisting>
119+
ROLLBACK;
120+
ROLLBACK TO SAVEPOINT sp1;
121+
</programlisting>
122+
Choosing <command>ROLLBACK</command> will abort everything, including
123+
value 1, whereas <command>ROLLBACK TO SAVEPOINT sp1</command> will retain
124+
value 1 and allow the transaction to continue.
125+
</para>
126+
107127
</refsect1>
108128

109129
<refsect1>

‎doc/src/sgml/ref/rollback_to.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,9 @@ ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] <replaceable>savepoint_name</re
3535

3636
<para>
3737
Roll back all commands that were executed after the savepoint was
38-
established. The savepoint remains valid and can be rolled back to
39-
again later, if needed.
38+
established and then start a new subtransaction at the same transaction level.
39+
The savepoint remains valid and can be rolled back to again later,
40+
if needed.
4041
</para>
4142

4243
<para>

‎doc/src/sgml/wal.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,9 @@
44
<title>Reliability and the Write-Ahead Log</title>
55

66
<para>
7-
This chapter explains how the Write-Ahead Log is used to obtain
8-
efficient, reliable operation.
7+
This chapter explains how to control the reliability of
8+
<productname>PostgreSQL</productname>, including details about the
9+
Write-Ahead Log.
910
</para>
1011

1112
<sect1 id="wal-reliability">
@@ -811,4 +812,5 @@
811812
seem to be a problem in practice.
812813
</para>
813814
</sect1>
815+
814816
</chapter>

0 commit comments

Comments
 (0)
0