Re: Two-phase commit issues
| От | jordan |
|---|---|
| Тема | Re: Two-phase commit issues |
| Дата | |
| Msg-id | 1116610151.8701.52.camel@jordan.geofocus.com обсуждение исходный текст |
| Ответ на | Re: Two-phase commit issues (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
Exactly. A 2PC expects every participant that makes it to the prepare to commit phase to survive a server restart, controlleror otherwise. Anything less is not 2PC. <br /><br /> Jordan Henderson<br /><br /> On Fri, 2005-05-20 at 12:07-0400, Tom Lane wrote: <blockquote type="CITE"><pre> <font color="#000000">Bruce Momjian <<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>> writes:</font> <font color="#000000">> I am a little confused by this. How does two-phase commit add extra</font> <font color="#000000">> requirements on crash recovery?</font> <font color="#000000">Uh, that's more or less the entire *POINT*. Once an open transaction is</font> <font color="#000000">prepared, it's supposed to survive a server crash.</font> <font color="#000000"> regards, tom lane</font> <font color="#000000">---------------------------(end of broadcast)---------------------------</font> <font color="#000000">TIP 9: the planner will ignore your desire to choose an index scan if your</font> <font color="#000000"> joining column's datatypes do not match</font> </pre></blockquote>
В списке pgsql-hackers по дате отправления: