Re: Re: synchronous_commit and synchronous_replication Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Dimitri Fontaine <dimitri@2ndquadrant.fr>
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, Fujii Masao <masao.fujii@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Greg Stark <gsstark@mit.edu>, Simon Riggs <simon@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-04-05T08:44:09Z
Lists: pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: >> No, sorry about confusion. One GUC is better. What I'm wondering is >> why commit it *now*, because I think we didn't yet decide on what the >> supported behaviors supported in 9.1 should be. > > What do you mean by "supported behaviors"? Well, I'm thinking about Simon's patch that some decided on procedural grounds only that it was too late to apply in 9.1, and some others were saying that given the cost benefit ratio of such a small patch that the design had already been agreed on, it is legible for 9.1. I think that we just expressed opinions on the async|recv|fsync|apply patch, and that we've yet to reach a consensus and make a decision. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support