Re: two phase commit - Mailing list pgsql-general

From Ben
Subject Re: two phase commit
Date
Msg-id Pine.LNX.4.64.0707191546360.27105@localhost.localdomain
Whole thread Raw
In response to Re: two phase commit  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: two phase commit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Er, right.... I guess I should have asked if it's more likely to commit a
running transaction than a prepared one.... and it sounds like the answer
is "no". :)

On Thu, 19 Jul 2007, Tom Lane wrote:

> Ben <bench@silentmedia.com> writes:
>> I'm reading the description of PREPARE TRANSACTION, and I see this:
>> "...its state is fully stored on disk, and there is a very high
>> probability that it can be committed successfully..."
>
>> What corner case reduces 2pc from "guaranteed" to "very high probability"?
>
> Well, for example, someone drops a nuke on your data center ...
>
> Barring hardware failure, OS failure, or irrecoverable database crash,
> the only condition I can think of that would prevent COMMIT PREPARED
> from succeeding is out-of-disk-space on the WAL drive.  Which is a PANIC
> condition anyway, and thus might be classed with database crashes,
> although it's not irrecoverable so long as the admin can free up some
> disk space.
>
>             regards, tom lane
>

pgsql-general by date:

Previous
From: Jeff Davis
Date:
Subject: Re: two phase commit
Next
From: Tom Lane
Date:
Subject: Re: two phase commit