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 21:33:47
Message-ID: 46954CBB.9010804@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Sullivan wrote:
> On Wed, Jul 11, 2007 at 09:26:34PM +0100, Heikki Linnakangas wrote:
>> 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.
>
> So then in this sort of case, it isn't _really_ safe to delete those
> files, because the commitment you made before crash when you accepted
> a PREPARE TRANSACTION is going to be gone, which violates the 2PC
> rules.

Yes, though if neither you nor the transaction manager can connect, you
don't have much choice.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-07-11 21:41:45 Re: 2PC-induced lockup
Previous Message Simon Riggs 2007-07-11 21:28:25 Re: "Running readonly queried on PITR slaves" statusupdate