On 2 February 2015 at 14:32, Geoff Winkless <pgsqlad...@geoff.dj> wrote: > 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 :(
Replying to my own message, because it occurs to me I might be being stupid (surely not :) ) When you say "this will still lock the unmodified row" did you mean just that it's locked to _other_ processes until commit? That would be much less impactful. Geoff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
