Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Date: 2015-05-20 19:07:56
Message-ID: CAM3SWZSP3YxqKXaQ2aa6TFwhD1TuaeOPqimOgH_RTK1ZsDXSow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Wed, May 20, 2015 at 11:26 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Even if maybe not directly under the guise of exclusion constraints
> themselves, but I do think it's an interesting way to more easily allow
> to implement unique constraints on !amcanunique type indexes. Or, more
> interestingly, for unique keys spanning partitions

Alright, then. It's just that at one point people seemed to think that
upsert should support exclusion constraints, and that position was, at
the time, lacking a good justification IMV. What you talk about here
seems much more practical than generalizing upsert to work with
exclusion constraints. You're talking about exclusion constraints as
an implementation detail of something interesting, which I had not
considered.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andres Freund 2015-05-20 19:09:23 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Previous Message Andres Freund 2015-05-20 18:26:17 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-05-20 19:07:58 Re: jsonb concatenate operator's semantics seem questionable
Previous Message Tom Lane 2015-05-20 19:03:44 Re: Problems with question marks in operators (JDBC, ECPG, ...)