Re: 2PC-induced lockup - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: 2PC-induced lockup
Date
Msg-id 46953CFA.5070404@enterprisedb.com
Whole thread Raw
In response to Re: 2PC-induced lockup  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: 2PC-induced lockup  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-hackers
Andrew Sullivan wrote:
> On Wed, Jul 11, 2007 at 06:15:12PM +0100, Heikki Linnakangas wrote:
>> It's effectively the same as manually issuing a ROLLBACK PREPARED. It 
>> will brake the atomicity of the global transaction, if some branches of 
>> that global transaction in other resource managers have already been 
>> committed.
> 
> But how do you know which file to delete?  Is it keyed to the
> transaction identifier or something?

The xid is encoded in the filename. If you can't start up the database 
and look at pg_locks, you can't do much other than guess.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: 2PC-induced lockup
Next
From: Andrew Sullivan
Date:
Subject: Re: 2PC-induced lockup