Re: 2-phase commit

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas SB SD
Тема Re: 2-phase commit
Дата
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4962022@m0114.s-mxs.net
обсуждение исходный текст
Ответ на 2-phase commit  (Andrew Sullivan <andrew@libertyrms.info>)
Список pgsql-hackers
> > >         Master          Slave
> > >         ------          -----
> > >         commit ready-->
> > >                         <--OK
> > >         commit done->XX
> > >
> > > is the "commit done" message needed ?
> >
> > Of course ... how else will the Slave commit?  From my
> understanding, the
> > concept is that the master sends a commit ready to the
> slave, but the OK
> > back is that "OK, I'm ready to commit whenever you are", at
> which point
> > the master does its commit and tells the slave to do its ...
>
> Or the slave could reject the request.

At this point only because of a hardware error. In case of network
problems the "commit done" eighter did not reach the slave or the "success"
answer did not reach the master.

That is what it's all about. Phase 2 is supposed to be low overhead and very
fast to allow keeping the time window for failure (that produces in-doubt
transactions) as short as possible.

Andreas


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Zeugswetter Andreas SB SD"
Дата:
Сообщение: Re: 2-phase commit
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: 2-phase commit