On Sat, Sep 21, 2013 at 7:22 PM, Peter Geoghegan <p...@heroku.com> wrote: > So because this isn't a tuple-level lock - it's really a value-level > lock - LockTuple() is not called by the btree code at all, and so > arbitration of who gets the lock is, as I've said, essentially > undefined.
Addendum: It isn't even a value-level lock, because the buffer locks are of course released before the XactLockTableWait() call. It's a simple attempt to acquire a shared lock on an xid. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
