rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-27 22:41:57 +02:00
Code Issues Packages Projects Releases Wiki Activity

Revert erroroneous commit 834b80464d; my apologies

Browse Source 
Backpatch-through: master
This commit is contained in:
Bruce Momjian 2020-03-31 17:32:00 -04:00
parent 834b80464d
commit c2da793fd2
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/mvcc.sgml
View File

@ -1039,9 +1039,9 @@ ERROR: could not serialize access due to read/write dependencies among transact
</tip>
<para>
Once acquired, a lock is normally held until the end of the transaction. But if a
Once acquired, a lock is normally held till end of transaction. But if a
lock is acquired after establishing a savepoint, the lock is released
immediately if the savepoint is rolled back. This is consistent with
immediately if the savepoint is rolled back to. This is consistent with
the principle that <command>ROLLBACK</command> cancels all effects of the
commands since the savepoint. The same holds for locks acquired within a
<application>PL/pgSQL</application> exception block: an error escape from the block
@ -1178,10 +1178,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
conflicting locks on the same row, even in different subtransactions;
but other than that, two transactions can never hold conflicting locks
on the same row. Row-level locks do not affect data querying; they
block only <emphasis>writers and lockers</emphasis> to the same
row. Row-level locks are released at transaction end or during
savepoint rollback, just like table-level locks.
block only <emphasis>writers and lockers</emphasis> to the same row.
</para>
<variablelist>