| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | 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:06:24 |
| Message-ID: | 20150527140624.GB5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2015-05-27 14:30:09 | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
| Previous Message | Stephen Frost | 2015-05-27 13:51:55 | Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-27 14:14:47 | Re: Triggers on transaction? |
| Previous Message | Garick Hamlin | 2015-05-27 13:54:37 | Re: Run pgindent now? |