From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
Date: | 2015-05-27 14:30:09 |
Message-ID: | CANP8+jLSvqqd_TrusWr=MiPxMf6c1a9sw7CxzX=rCZJMwmw_Og@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 27 May 2015 at 15:06, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-27 14:38:35 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |
Previous Message | Alvaro Herrera | 2015-05-27 14:06:24 | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-27 14:38:35 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |
Previous Message | Tom Lane | 2015-05-27 14:14:47 | Re: Triggers on transaction? |