Op 13-04-2022 om 20:00 schreef Alvaro Herrera:
On 2022-Apr-04, PG Doc comments form wrote:
I propose that it would be useful to explicitly state that `SELECT FOR KEY
SHARE` AND `SELECT FOR NO KEY UPDATE` commands also acquire the ROW SHARE
table level lock on target table(s). That is:
```
Confl
On 2022-Apr-04, PG Doc comments form wrote:
> I propose that it would be useful to explicitly state that `SELECT FOR KEY
> SHARE` AND `SELECT FOR NO KEY UPDATE` commands also acquire the ROW SHARE
> table level lock on target table(s). That is:
> ```
> Conflicts with the EXCLUSIVE and ACCESS EXCLU
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/explicit-locking.html
Description:
The ROW SHARE table level lock modes section currently states:
```
Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
The SELECT FOR UPDATE a
