Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
От
Fujii Masao
Тема
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication.
Дата
Msg-id
AANLkTinC2+OuVQdHWVRfDLOTA7Z1n2JZdbUsrgCmvmJN@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Andrew Dunstan <andrew@dunslane.net>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Andrew Dunstan <andrew@dunslane.net>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Aidan Van Dyk <aidan@highrise.ca>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Andrew Dunstan <andrew@dunslane.net>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Andrew Dunstan <andrew@dunslane.net>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. Alvaro Herrera <alvherre@commandprompt.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. MARK CALLAGHAN <mdcallag@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Aidan Van Dyk <aidan@highrise.ca>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. Simon Riggs <simon@2ndQuadrant.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Fujii Masao <masao.fujii@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Greg Stark <gsstark@mit.edu>
Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous
replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient
transaction-controlled synchronous replication. "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. MARK CALLAGHAN <mdcallag@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Markus Wanner <markus@bluegap.ch>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. MARK CALLAGHAN <mdcallag@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Robert Haas <robertmhaas@gmail.com>
Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled
synchronous replication. Aidan Van Dyk <aidan@highrise.ca>
On Sat, Mar 19, 2011 at 4:29 AM, Simon Riggs wrote: > 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 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. I'm not sure what's the problem with seeing from the standby the data which is not visible on the master yet? And, I'm really not sure whether that problem can be solved by making the data visible on the master before the standby. If we really want to see the consistent data from each node, we should implement and use a cluster-wide snapshot as well as Postgres-XC does. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления