On 30 January 2015 at 21:58, Peter Geoghegan <p...@heroku.com> wrote: > On Fri, Jan 30, 2015 at 6:59 AM, Geoff Winkless <pgsqlad...@geoff.dj> wrote: >> I suppose there's no reason why we couldn't use a no-op ON CONFLICT >> UPDATE anyway > > Right. IGNORE isn't really all that compelling for that reason. Note > that this will still lock the unmodified row, though.
Mmmf. So I would have to make sure that my source tuples were unique before doing the INSERT (otherwise the first ON CONFLICT UPDATE for a tuple would block any other)? That's potentially very slow :( When you say that you can't add exclusion constraints later, do you mean from a coding point of view or just because people would get confused whether exclusion constraints could be IGNOREd or not? Geoff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
