| From: | jordan <jordan_henders(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Two-phase commit issues |
| Date: | 2005-05-20 17:29:10 |
| Message-ID: | 1116610151.8701.52.camel@jordan.geofocus.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Exactly. A 2PC expects every participant that makes it to the prepare
to commit phase to survive a server restart, controller or otherwise.
Anything less is not 2PC.
Jordan Henderson
On Fri, 2005-05-20 at 12:07 -0400, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I am a little confused by this. How does two-phase commit add extra
> > requirements on crash recovery?
>
> Uh, that's more or less the entire *POINT*. Once an open transaction is
> prepared, it's supposed to survive a server crash.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
| From | Date | Subject | |
|---|---|---|---|
| Next Message | José Orlando Pereira | 2005-05-20 17:34:53 | Re: Two-phase commit issues |
| Previous Message | Tom Lane | 2005-05-20 17:14:14 | Re: Two-phase commit issues |