KEY UPDATE / UPDATE / NO KEY UPDATE distinction vs. README.tuplock - Mailing list pgsql-hackers

From Florian Pflug
Subject KEY UPDATE / UPDATE / NO KEY UPDATE distinction vs. README.tuplock
Date
Msg-id 3FBFACF5-B423-42EA-A2F9-D6281545A1FE@phlo.org
Whole thread Raw
Responses Re: KEY UPDATE / UPDATE / NO KEY UPDATE distinction vs. README.tuplock
List pgsql-hackers
Hi,

It seems that README.tuplock never got updated when the KEY SHARE patch's
lock level were changed from being KEY UPDATE / UPDATE / SHARE / KEY SHARE
to UPDATE / NO KEY UPDATE / SHARE / KEY SHARE.

Thus, as it stands, that file implies that SELECT FOR UPDATE obtains a
weaker lock than an actual UPDATE might take (if that update modifies key
columns) -- according to README.tuplock, the former doesn't conflict with
KEY SHARE while the actual UPDATE would.

But this isn't actually the case in the committed version of the patch -
one now needs to explicitly request that weaker lock level with SELECT FOR
NO KEY UPDATE.

The attached patch updated README.tuplock accordingly.

best regards,
Florian Pflug

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: idea: allow AS label inside ROW constructor
Next
From: Fujii Masao
Date:
Subject: Re: pg_receivexlog --status-interval add fsync feedback