Re: 2PC-induced lockup

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 2PC-induced lockup
Date: 2007-07-11 20:26:34
Message-ID: 46953CFA.5070404@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2007-07-11 20:54:13 Re: 2PC-induced lockup
Previous Message Peter Eisentraut 2007-07-11 20:08:12 Re: 2PC-induced lockup