Re: Two-phase commit

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Two-phase commit
Date: 2004-10-08 06:01:18
Message-ID: 41662D2E.8010104@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Heikki Linnakangas wrote:
> On Thu, 7 Oct 2004, Oliver Jowett wrote:
>
>> Probably the next question is, do we want a database-side timeout on
>> how long prepared txns can stay alive before being summarily rolled back?
>
>
> That sounds very dangerous to me. You could end up breaking global
> atomicity if some other resource in the global transaction committed.

Right. You wouldn't enable it lightly..

> The transaction monitor can do timeouts if necessary, and a super user
> has to resolve the in-doubt transactions if the TM crashes non-recoverably.

Some systems may prefer short-term availability over atomicity. Putting
a human in the loop when doing recovery hurts your availability.

If pg_prepared_xacts had a time-of-preparation column, it would be
possible to put the timeout policy in an external client. Perhaps that's
a better solution?

-O

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yann Michel 2004-10-08 07:26:19 Re: plans for bitmap indexes?
Previous Message Tom Lane 2004-10-08 05:38:19 Re: Security implications of config-file-location patch

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2004-10-08 11:24:55 Re: [psql] Setting the PROMPT on command line
Previous Message Tom Lane 2004-10-08 04:26:06 Re: [PATCHES] HP-UX PA-RISC/Itanium 64-bit Patch and HP-UX