Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: update behavior
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <0D31EA2C-9038-4C2D-A4CD-E602809F16CC@elevated-dev.com>
Date: Thu, 19 Jun 2025 11:48:30 -0600
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <58598CFA-7C0F-4629-9D54-C366CEC8CCB4@elevated-dev.com>
References: <75F792AF-58DF-4559-A2E8-C89060D1E94E@elevated-dev.com>
 <CAKFQuwbwAbbk6KUKXyX2VxpX3aUDhS5Zd__2JKQXdhH5zHaB4g@mail.gmail.com>
 <BE13CDCE-A689-4627-9B7F-572765CD9FBB@elevated-dev.com>
 <0D31EA2C-9038-4C2D-A4CD-E602809F16CC@elevated-dev.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>,
 Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/58598CFA-7C0F-4629-9D54-C366CEC8CCB4%40elevated-dev.com>
Precedence: bulk

> On Jun 19, 2025, at 11:39=E2=80=AFAM, Scott Ribe =
<scott_ribe@elevated-dev.com> wrote:
>=20
>> On Jun 19, 2025, at 11:34=E2=80=AFAM, Scott Ribe =
<scott_ribe@elevated-dev.com> wrote:
>>=20
>>> On Jun 19, 2025, at 11:31=E2=80=AFAM, David G. Johnston =
<david.g.johnston@gmail.com> wrote:
>>>=20
>>> Correct.  You need a trigger to prevent the update.  There is one =
provided: suppress_redundant_updates_trigger()
>>=20
>> Or, in my case that prompted this question, I need a WHERE clause for =
the ON CONFLICT UPDATE...
>=20
> Wait, should suppress_redundant_updates_trigger be used even in this =
case? Would it suppress the update before the constraint checks and =
invocation of the ON CONFLICT clause???

Or no, duh, this starts with an INSERT where that won't be run, there is =
no UPDATE until after the constraint violation, but then at that point =
it would suppress the update?