Re: pgsql: Improve concurrency of foreign key locking - Mailing list pgsql-committers

From Bernd Helmle
Subject Re: pgsql: Improve concurrency of foreign key locking
Date
Msg-id BF7DDADB6810626A64FBE478@apophis.credativ.lan
Whole thread Raw
In response to pgsql: Improve concurrency of foreign key locking  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-committers

--On 23. Januar 2013 15:12:00 +0000 Alvaro Herrera
<alvherre@alvh.no-ip.org> wrote:

> This patch introduces two additional lock modes for tuples: "SELECT FOR
> KEY SHARE" and "SELECT FOR NO KEY UPDATE".  These don't block each
> other, in contrast with already existing "SELECT FOR SHARE" and "SELECT
> FOR UPDATE".  UPDATE commands that do not modify the values stored in
> the columns that are part of the key of the tuple now grab a SELECT FOR
> NO KEY UPDATE lock on the tuple, allowing them to proceed concurrently
> with tuple locks of the FOR KEY SHARE variety.

Out of curiousity, shouldn't we update chapter 13.3.2 in the docs to
mention the additional new lock modes, too?


--
Thanks

    Bernd


pgsql-committers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: pgsql: Add --aggregate-interval option.
Next
From: Magnus Hagander
Date:
Subject: pgsql: Properly zero-pad the day-of-year part of the win32 build number