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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Date: 2014-09-29 04:03:21
Message-ID: CAM3SWZTyw0Oq6ODzLLobM3-uWaRggNAoVoHy6mQAuSUkBP4DnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 28, 2014 at 8:53 PM, Craig Ringer <craig(at)2ndquadrant(dot)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.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2014-09-29 04:14:32 Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Previous Message Craig Ringer 2014-09-29 03:53:32 Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}