| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Subject: | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Date: | 2014-09-29 22:05:46 |
| Message-ID: | CAM3SWZRM51RJ3j6PnuixVkoACPdKwS5V47iUADmRakDnYS1Wtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 29, 2014 at 3:02 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> That'll make it really hard to actually implement real MERGE.
>
> Because suddenly there's no way for the user to know whether he's
> written a ON condition that can implement UPSERT like properties
> (i.e. the *precise* column list of an index) or not.
Exactly. The difficulty isn't doing what Kevin says so much as doing
so and then at a later date taking that thing and making it into a
fully featured MERGE. We'll be painted into a corner. That's bad,
because as I've said I think we need MERGE too (just far less
urgently).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2014-09-29 22:08:36 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Previous Message | Peter Geoghegan | 2014-09-29 22:04:02 | Valgrind warnings in master branch ("Invalid read of size 8") originating within CreatePolicy() |