Re: Synchronous replication - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Synchronous replication
Date
Msg-id AANLkTimVz-849Fn1xCc=OCmg9YMXsnLxS-2Qy3ykzZPG@mail.gmail.com
Whole thread Raw
In response to Re: Synchronous replication  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Synchronous replication  (Robert Haas <robertmhaas@gmail.com>)
Re: Synchronous replication  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
On Mon, Aug 2, 2010 at 7:53 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Let's not get *the manner of specifying the policy* confused with *the
> need to update the policy when the master changes*.  It doesn't seem
> likely you would want the same value for  synchronous_standbys on all
> your machines.  In the most common configuration, you'd probably have:
>
> on A: synchronous_standbys=B
> on B: synchronous_standbys=A

Oh, true. But, what if we have another synchronous standby called C?
We specify the policy as follows?:

on A: synchronous_standbys=B,C
on B: synchronous_standbys=A,C
on C: synchronous_standbys=A,B

We would need to change the setting on both A and B when we want to
change the name of the third standby from C to D, for example. No?

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Postgres as Historian
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: lock_timeout GUC patch - Review