Re: Possible PANIC in PostPrepare_Locks

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Possible PANIC in PostPrepare_Locks
Date: 2013-01-11 09:36:24
Message-ID: 50EFDD18.7030508@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vlad Arkhipov 2013-01-11 09:47:40 Get current query in a trigger function
Previous Message Sandeep Thakkar 2013-01-11 07:34:37 Re: Bug: Windows installer modifies ACLs on the whole volume