Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.
Date
Msg-id CANP8+jLSvqqd_TrusWr=MiPxMf6c1a9sw7CxzX=rCZJMwmw_Og@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 27 May 2015 at 15:06, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Simon Riggs wrote:

> What I think should happen is that the command tag should vary according to
> whether an INSERT or an UPDATE was performed, so we get a visible
> difference without any new tags.

The problem with doing that is that the same command might have updated
some tuples and inserted others.  Also, we build the tag before the
command is executed.

Hmm,  I assumed the various anomalies meant that it was a single row only command...

Anybody know where the various anomalies are documented? e.g. how if an insert has been committed that we can't yet see whether we are allowed to update that using same rules as update. 

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Triggers on transaction?
Next
From: Stephen Frost
Date:
Subject: Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension