Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
От | Simon Riggs |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Дата | |
Msg-id | 1300476590.18619.18115.camel@ebony обсуждение исходный текст |
Ответ на | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. (Markus Wanner <markus@bluegap.ch>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication.
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Список | pgsql-hackers |
On Fri, 2011-03-18 at 20:19 +0100, Markus Wanner wrote: > Simon, > > On 03/18/2011 05:19 PM, Simon Riggs wrote: > >>> Simon Riggs<simon@2ndQuadrant.com> wrote: > >>>> In PostgreSQL other users cannot observe the commit until an > >>>> acknowledgement has been received. > > On other nodes as well? To me that means the standby needs to hold back > COMMIT of an ACKed transaction, until receives a re-ACK from the master, > that it committed the transaction there. How else could the slave know > when to commit its ACKed transactions? We could do that easily enough, actually, if we wished. Do we wish? > > No, only in the case where you choose not to failover to the standby > > when you crash, which would be a fairly strange choice after the effort > > to set up the standby. In a correctly configured and operated cluster > > what I say above is fully correct and needs no addendum. > > If you don't failover, how can the standby be ahead of the master, given > it takes measures not to be during normal operation? > > Eager to understand... ;-) > > Regards > > Markus -- Simon Riggs http://www.2ndQuadrant.com/books/PostgreSQL Development, 24x7 Support, Training and Services
В списке pgsql-hackers по дате отправления: