Re: update behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Subject: Re: update behavior
From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
Date: Thu, 19 Jun 2025 11:34:19 -0600
Cc: Pgsql-admin <pgsql-admin@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAKFQuwbwAbbk6KUKXyX2VxpX3aUDhS5Zd__2JKQXdhH5zHaB4g@mail.gmail.com>
References: <75F792AF-58DF-4559-A2E8-C89060D1E94E@elevated-dev.com> <CAKFQuwbwAbbk6KUKXyX2VxpX3aUDhS5Zd__2JKQXdhH5zHaB4g@mail.gmail.com>

> 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...

Follow-Ups:
- Re: update behavior
  - From: Scott Ribe

References:
- update behavior
  - From: Scott Ribe
- Re: update behavior
  - From: David G. Johnston

Prev by Date: Re: update behavior
Next by Date: Re: update behavior
Previous by thread: Re: update behavior
Next by thread: Re: update behavior
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Home] [Postgresql General] [Postgresql Performance] [Postgresql PHP] [Postgresql Jobs] [PHP Users] [PHP Databases] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Yosemite Forum]

Powered by Linux