Horton

Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}

Craig Ringer <craig@2ndquadrant.com>

View thread View on postgr.es
From: Craig Ringer <craig@2ndquadrant.com>
To: Peter Geoghegan <pg@heroku.com>
Cc: Gavin Flower <GavinFlower@archidevsys.co.nz>, Simon Riggs <simon@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-09-29T04:14:32Z
Lists: pgsql-hackers 
On 09/29/2014 12:03 PM, Peter Geoghegan wrote:
> On Sun, Sep 28, 2014 at 8:53 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
>> there's an alarming lack of concern for concurrency, just a couple of
>> links to :
>>
>> http://www.mssqltips.com/sqlservertip/3074/use-caution-with-sql-servers-merge-statement/
>>
>> (BTW, that article contains some useful information about corner cases
>> any upsert approach should test and deal with).
> 
> Did you find some of those links from my pgCon slides, or
> independently? I'm well aware of those issues, FWIW. Avoiding
> repeating the mistakes of others is something that I thought about
> from an early stage.

Independently. I'm very glad to see you've looked over those issues.

-- 
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Commits

  1. Change the way we mark tuples as frozen.

  2. Add documentation for data-modifying statements in WITH clauses.