diff options
| author | Alvaro Herrera | 2022-04-14 19:52:20 +0000 |
|---|---|---|
| committer | Alvaro Herrera | 2022-04-14 19:52:20 +0000 |
| commit | 275e719d910459db747346a51d56185e2440763b (patch) | |
| tree | 172474bc502ef42e060dfe9be5e01ebf9f5b0fbb | |
| parent | 5bb2b6abc8d6cf120a814317816e4384bcbb9c1e (diff) | |
Reword text on ROW SHARE lock as acquired by SELECT FOR <lock>
It was missing lock levels FOR KEY SHARE and FOR NO KEY EXCLUSIVE; but
also SELECT FOR UPDATE is not a command separate from SELECT, as the
original text implied. It is clearer to state that FOR <lock strength>
is an option of regular SELECT.
Per suggestion from Joey Bodoia <[email protected]>
Reviewed-by: Joey Bodoia <[email protected]> (offlist)
Reviewed-by: Erikjan Rijkers <[email protected]>
Discussion: https://postgr.es/m/[email protected]
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 905460723c..341fea524a 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -932,12 +932,14 @@ ERROR: could not serialize access due to read/write dependencies among transact </para> <para> - The <command>SELECT FOR UPDATE</command> and - <command>SELECT FOR SHARE</command> commands acquire a - lock of this mode on the target table(s) (in addition to - <literal>ACCESS SHARE</literal> locks on any other tables - that are referenced but not selected - <option>FOR UPDATE/FOR SHARE</option>). + The <command>SELECT</command> command acquires a lock of this mode + on all tables on which one of the <option>FOR UPDATE</option>, + <option>FOR NO KEY UPDATE</option>, + <option>FOR SHARE</option>, or + <option>FOR KEY SHARE</option> options is specified + (in addition to <literal>ACCESS SHARE</literal> locks on any other + tables that are referenced without any explicit + <option>FOR ...</option> locking option). </para> </listitem> </varlistentry> |