Simon Riggs <si...@2ndquadrant.com> writes:
> On Wed, 2011-03-02 at 22:10 +0200, Heikki Linnakangas wrote:
>> Fair enough. All I'm saying is that if we end up shipping without that
>> parameter (implying allow_standalone_primary=on), we need to call the
>> feature something else. The GUCs and code can probably stay as it is,
>> but we shouldn't use the term "synchronous replication" in the
>> documentation, and release notes and such.
> allow_standalone_primary=off means "wait forever". It does nothing to
> reduce data loss since you can't replicate to a server that isn't there.
This is irrelevant to the point. The point is that sync rep implies
that we will not *tell a client* its data is committed unless the commit
is down to disk in two places. I agree with the people saying that not
having this parameter makes it not real sync rep.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
