> On Jun 19, 2025, at 11:34 AM, Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx> wrote: > >> On Jun 19, 2025, at 11:31 AM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote: >> >> Correct. You need a trigger to prevent the update. There is one provided: suppress_redundant_updates_trigger() > > Or, in my case that prompted this question, I need a WHERE clause for the ON CONFLICT UPDATE... 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???
