public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Scott Ribe <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: update behavior
Date: Thu, 19 Jun 2025 14:29:29 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAKFQuwbwAbbk6KUKXyX2VxpX3aUDhS5Zd__2JKQXdhH5zHaB4g@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Scott Ribe <[email protected]> writes:
> On Jun 19, 2025, at 11:39 AM, Scott Ribe <[email protected]> wrote:
>> 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?

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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: update behavior
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox