Quick Links

Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.

From:	Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To:	Stanislav Grozev <tacho(at)daemonz(dot)org>
Cc:	PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject:	Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Date:	2015-12-03 07:30:29
Message-ID:	CAB7nPqTjO4decSSm2DxeUrchX10SJ3GfKTddgBH42bvX5k4WjQ@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs

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

In response to

Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement. at 2015-11-30 11:43:12 from Stanislav Grozev

Responses

Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement. at 2015-12-03 07:33:28 from Stanislav Grozev
Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement. at 2015-12-03 08:19:58 from Dean Rasheed

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	Stanislav Grozev	2015-12-03 07:33:28	Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Previous Message	digoal	2015-12-03 01:20:48	BUG #13791: postgresql 9.5 beta2 brin bug (cann't auto update)