On 11.01.2013 04:16, Tom Lane wrote:
[explanation of a race condition]
Good catch.
Also, it looks like we'll need two code paths in PostPrepare_Locks to deal with the possibility that a conflicting entry already exists? I'm not sure this is possible, but I'm not sure it's not, either.
If I understand this correctly, that would mean that someone else is holding a lock that conflicts with the lock the transaction-being-prepared holds. That shouldn't happen.
- Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
