Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Date
Msg-id CAB7nPqTjO4decSSm2DxeUrchX10SJ3GfKTddgBH42bvX5k4WjQ@mail.gmail.com
Whole thread Raw
In response to Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Stanislav Grozev <tacho@daemonz.org>)
Responses Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Stanislav Grozev <tacho@daemonz.org>)
Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-bugs
Tree view 
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?
--
Michael

pgsql-bugs by date:

Previous
From: Paul Moore
Date:
Subject: Re: BUG #13788: compile error in generic_msvc.h
Next
From: Stanislav Grozev
Date:
Subject: Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.