Re: update behavior - Mailing list pgsql-admin

From Tom Lane
Subject Re: update behavior
Date
Msg-id 1483328.1750357769@sss.pgh.pa.us
Whole thread Raw
In response to Re: update behavior  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
Scott Ribe <scott_ribe@elevated-dev.com> writes:
> On Jun 19, 2025, at 11:39 AM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>> Wait, should suppress_redundant_updates_trigger be used even in this case? Would it suppress the update before the
constraintchecks 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? 

I believe we fire ON UPDATE triggers when an INSERT ON CONFLICT
takes an UPDATE action, so it should do what you want.  The
overhead tradeoff is yours to make.

            regards, tom lane



pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Re: update behavior
Next
From: Valere Binet
Date:
Subject: FATAL: connection requires a valid client certificate