Re: unique constraint violation on multiple-rows update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: unique constraint violation on multiple-rows update
Date: 2026-04-19 15:17:47
Message-ID: 4040650.1776611867@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> writes:
> Am Sun, Apr 19, 2026 at 06:54:02AM -0700 schrieb David G. Johnston:
>> You know about deferred constraints, you should use them here. This is one
>> of the key use cases motivating their existence.

> Indeed. I was of the mistaken impression that UNIQUE
> constraints were not deferrable ...

Once upon a time they were not, but we fixed that years ago.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Igor Korot 2026-04-19 20:27:46 Re: List of encodings
Previous Message Karsten Hilbert 2026-04-19 14:09:18 Re: unique constraint violation on multiple-rows update