> On 1 May 2026, at 7:35 AM, Laurenz Albe <[email protected]> wrote:
>
> Also, the behavior difference only occurs with ON CONFLICT DO NOTHING.
> If you use ON CONFLICT ... DO UPDATE ..., the update will block.
> That makes the behavior difference somewhat less bad in my eyes.
Yes, I had noticed that as well. In my case my goal is to both block and “do
nothing” if after blocking a matching row is found. If this behaviour isn’t
expected, I thought I could change to
ON CONFLICT DO UPDATE SET id = EXCLUDED.id
to essentially “do nothing” but I thought I would incur an actual update and I
wanted to avoid the churn I presumed that would include.
Kind regards,
Matt
