Re: The documentation for READ COMMITTED may be incomplete or wrong - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: The documentation for READ COMMITTED may be incomplete or wrong
Date
Msg-id CAJ7c6TM02_5dJ2VKrkGsbmDh-xVdZX8dwS9MLZtvMY3R8fAyVw@mail.gmail.com
Whole thread Raw
In response to Re: The documentation for READ COMMITTED may be incomplete or wrong  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

> I wonder what we got wrong.

One thing we noticed is that the description for EvalPlanQual may be wrong [1]:

"""
In UPDATE/DELETE, only the target relation needs to be handled this way.
In SELECT FOR UPDATE, there may be multiple relations flagged FOR UPDATE,
so we obtain lock on the current tuple version in each such relation before
executing the recheck.
"""

[1]: https://github.com/postgres/postgres/blob/master/src/backend/executor/README#L381

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: The documentation for READ COMMITTED may be incomplete or wrong
Next
From: "Tristan Partin"
Date:
Subject: Meson build updates