Re: Possible PANIC in PostPrepare_Locks - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Possible PANIC in PostPrepare_Locks
Date
Msg-id 50EFDD18.7030508@vmware.com
Whole thread Raw
In response to Possible PANIC in PostPrepare_Locks  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Possible PANIC in PostPrepare_Locks
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Sandeep Thakkar
Date:
Subject: Re: Bug: Windows installer modifies ACLs on the whole volume
Next
From: Vlad Arkhipov
Date:
Subject: Get current query in a trigger function