Re: update behavior

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

To: Tom Lane <tgl@xxxxxxxxxxxxx>
Subject: Re: update behavior
From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
Date: Mon, 23 Jun 2025 11:29:50 -0600
Cc: "David G. Johnston" <david.g.johnston@xxxxxxxxx>, Pgsql-admin <pgsql-admin@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <1483328.1750357769@sss.pgh.pa.us>
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> <58598CFA-7C0F-4629-9D54-C366CEC8CCB4@elevated-dev.com> <1483328.1750357769@sss.pgh.pa.us>

> On Jun 19, 2025, at 12:29 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> 
> I believe we fire ON UPDATE triggers when an INSERT ON CONFLICT
> takes an UPDATE action, so it should do what you want.

Tested, and confirmed, this morning.

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

Prev by Date: Re: FATAL: connection requires a valid client certificate
Next by Date: Re: 'Sharing' data across different database.
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