Fujii Masao <masao.fu...@gmail.com> writes:
> On Tue, Oct 5, 2010 at 2:06 AM, Aidan Van Dyk <ai...@highrise.ca> wrote:
>> I'm happy with the docs saying (maybe some what more politely):
>> Before configuring your master to be completly,
>> wait-fully-synchronous, make sure you have a slave capable of being
>> synchronous ready. Because if you've told it to never be
>> un-synchronous, it won't be.
> How can we take a base backup for that synchronous standby? You mean
> that we should disable the wait-forever option, start the master, take
> a base backup, shut down the master, enable the wait-forever option,
> start the master, and start the standby from that base backup?
I think the point here is that it's possible to have sync-rep
configurations in which it's impossible to take a base backup. That
doesn't seem to me to be unacceptable in itself. What *is* unacceptable
is to be unable to change the configuration to another state in which
you could take a base backup. Which is why "keep the config in a system
catalog" doesn't work.
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
