Re: Making joins involving ctid work for the benefit of UPSERT

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making joins involving ctid work for the benefit of UPSERT
Date: 2014-07-18 18:50:34
Message-ID: CAM3SWZS4vP0TfBjvK+Y2mYnZK+9Vx_zYcwgZGbvZTZGGtvC-Fg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 18, 2014 at 11:32 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> Well, maybe. If the genericity of this syntax isn't what people want,
> I may go with something else.

By the way, I didn't mention that there is now also the optional
ability to specify a "merge on" unique index directly in DML. It would
be much nicer to specify a sort key instead, but that might be tricky
in the general case. I imagine that other systems solve the problem by
being very restrictive in what will be (implicitly) accepted as a
merge-on index. Seemingly there are problems with all major SQL MERGE
implementations, so I don't necessarily expect to be able to draw
lessons from them in any way here.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Cochran 2014-07-18 18:54:34 Re: Proposal for updating src/timezone
Previous Message Robert Haas 2014-07-18 18:33:26 Re: RLS Design