diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2022-04-14 21:52:20 +0200 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2022-04-14 21:52:20 +0200 |
commit | 275e719d910459db747346a51d56185e2440763b (patch) | |
tree | 172474bc502ef42e060dfe9be5e01ebf9f5b0fbb /src/backend/parser/parse_expr.c | |
parent | 5bb2b6abc8d6cf120a814317816e4384bcbb9c1e (diff) | |
download | postgresql-275e719d910459db747346a51d56185e2440763b.tar.gz postgresql-275e719d910459db747346a51d56185e2440763b.zip |
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 <jbodoia21@cmc.edu>
Reviewed-by: Joey Bodoia <jbodoia21@cmc.edu> (offlist)
Reviewed-by: Erikjan Rijkers <er@xs4all.nl>
Discussion: https://postgr.es/m/164908765512.682.17348032020747341013@wrigleys.postgresql.org
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions