Postgres Pro
Downloads
Home   >   mailing lists

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

From Andres Freund
Subject Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Date
Msg-id 20151209215511.GB14789@awork2.anarazel.de
Whole thread Raw
In response to Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
Tree view 
On 2015-12-09 13:52:35 -0800, Peter Geoghegan wrote:
> On Wed, Dec 9, 2015 at 1:43 PM, Andres Freund <andres@anarazel.de> wrote:
> > Works for me. I'll add a short comment before the ExecUpdate() detailing
> > that the row could, in rather uncommon cases, be updated by that
> > point. Adding an extra parameter to ExecUpdate() + additional concerns
> > to it's already nontrivial HTSV codepath doesn't seem worth it to
> > me.
>
> HeapTupleSatisfiesVacuum? What of it?

Err, HTSU, via heap_update()'s result.

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Next
From: Peter Geoghegan
Date:
Subject: Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.