Postgres Pro
Downloads
Home   >   mailing lists

Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement. - Mailing list pgsql-bugs

From Dean Rasheed
Subject Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Date
Msg-id CAEZATCXxhKui4hCMXGyeWUeo-pTS7r4BwfzjkM7v0sOvLiAETA@mail.gmail.com
Whole thread Raw
In response to Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Tree view 
On 3 December 2015 at 07:30, Michael Paquier <michael.paquier@gmail.com> wrote:
> On Mon, Nov 30, 2015 at 8:43 PM, Stanislav Grozev wrote:
>> If we do an UPSERT instead, watch how OLD and NEW are the same (NEW):
>
> AFAIK, that's the expected behavior. AFTER UPDATE triggers firing for
> ON CONFLICT DO UPDATE will see the same NEW and OLD values. Comments
> from others?

That's not what I would expect. I would expect it to be consistent
with AFTER triggers firing after a plain UPDATE, and also with BEFORE
triggers for ON CONFLICT DO UPDATE.

Regards,
Dean

pgsql-bugs by date:

Previous
From: Stanislav Grozev
Date:
Subject: Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Next
From: otheus uibk
Date:
Subject: Possible bug: ALTER TABLE x DROP COLUMN y "column ... does not exist" then it does