| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Re: INSERT ... ON CONFLICT syntax issues |
| Date: | 2015-04-26 18:19:23 |
| Message-ID: | CAM3SWZQHSj1FA69grqRsu0Pq-vXJAVhsHu-ZtxCYOyik39SDAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 26, 2015 at 11:08 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> I don't want to accept something that automatically merges the
>> excluded tuple (e.g., "SET (*) = EXLCUDED.*"), for reasons outlined
>> here: https://wiki.postgresql.org/wiki/UPSERT#VoltDB.27s_UPSERT
>
> Perhaps I'm missing it, but the reasons that I see there appear to be:
>
> "It'd be like SELECT *" and "we'd have to decide what to do about the
> value for unspecified columns". As for the latter- we have to do that
> *anyway*, no? What happens if you do:
>
> INSERT INTO mytable (foo, bar, baz, bat) VALUES ('key1','key2','val1','val2')
> ON CONFLICT (foo) UPDATE SET (baz) = (EXCLUDED.baz);
>
> ?
It's like any other UPDATE - the values of columns not appearing in
the targetlist are unchanged from the original row version now
superseded. It doesn't matter that you had some other values in the
INSERT. You only get what you ask for.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-04-26 18:28:51 | Re: PATCH: default_index_tablespace |
| Previous Message | Stephen Frost | 2015-04-26 18:16:31 | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |