Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date: 2026-09-13 15:14:05
Message-ID: 27CEBAE2-FF0A-4D7D-909D-DCDC9806091F@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Dean,

On 13 Sep 2026, Dean Rasheed wrote:
> v4 also takes a predicate lock for
> deferred exclusion constraints

The fetch is inside if (conflictTid), and the deferred exclusion checks
pass NULL, so they do not acquire additional predicate locks IIUC.

+1 to v4

Thank you!

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-09-13 15:28:49 Re: Distinguish publication exclusions in object addresses
Previous Message Ayush Tiwari 2026-09-13 14:54:58 Re: [BUG] ON CONFLICT DO UPDATE SET x = EXCLUDED.<virtual-generated-column> errors or silently writes NULL