Re: 2-phase commit
От | Rod Taylor |
---|---|
Тема | Re: 2-phase commit |
Дата | |
Msg-id | 1064867320.61134.116.camel@jester обсуждение исходный текст |
Ответ на | Re: 2-phase commit (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-hackers |
On Mon, 2003-09-29 at 15:55, Peter Eisentraut wrote: > Manfred Spraul writes: > > > Ok. Lets assume one coordinator, two partitipants. > > Global commit send to both by coordinator. One replies with ok, the > > other one remains silent. > > What should the coordinator do? It can't fail the transaction - the > > first partitipant has commited its part. It can't complete the > > transaction, because the ok from the 2nd partitipant is still outstanding. > > If a participant doesn't reply in an orderly fashion (say, after timeout), > it just gets kicked out of the whole mechanism. That isn't the > interesting part. The interesting part is what happens when the > coordinator fails. The hot-standby coordinator picks up where the first one left off. Just like when the participant fails the hot-standby for that participant steps up to the plate. For the application server side in Java, I believe the standard is OTS (Object Transaction Service).
В списке pgsql-hackers по дате отправления: