From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: two phase commit |
Date: | 2007-07-21 00:17:00 |
Message-ID: | 1184977020.16532.223.camel@dogma.ljc.laika.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2007-07-20 at 15:26 -0400, Andrew Sullivan wrote:
> On Thu, Jul 19, 2007 at 03:13:27PM -0700, Ben wrote:
> > What corner case reduces 2pc from "guaranteed" to "very high probability"?
> > Is the worry if somebody leaves transactions in a prepared state for
> > weeks, only to find that deadlock issues has arrisen at final commit time?
>
> That's not the worry, no. But something _else_ could happen. For
> instance, recently it turned out that there was a way, using 2PC, to
> lock everybody out of the database. The only remedy to that at the
> moment is to blow away all the PREPAREd transactions, which could
> mean you lose something that was already committed to.
>
To clarify, I think you're referring to this:
http://archives.postgresql.org/pgsql-hackers/2007-07/msg00245.php
which can only be done as superuser locking a system table.
I would classify that as a "catastrophic" problem, since it involves
manually modifying $PGDATA.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Perry Smith | 2007-07-21 00:18:29 | Re: Foreign key constraint question |
Previous Message | Jeff Davis | 2007-07-21 00:01:45 | Re: Foreign key constraint question |