Fujii Masao wrote:
> On Wed, Feb 10, 2010 at 8:16 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> If they want to implement the warm standby using the (new) built-in
>> logic to keep retrying restore_command, they would set
>> standby_mode='on'. standby_mode='on' doesn't imply streaming replication.
> But if we fail in restoring the archived WAL file, "standby_mode = on"
> *always* tries to start streaming replication.
Hmm, somehow I thought it doesn't if you don't set primary_conninfo. I
think that's the way it should work, ie. if primary_conninfo is not set,
don't launch walreceiver but just keep trying to restore from the archive.
In response to
pgsql-hackers by date
|Next:||From: Fujii Masao||Date: 2010-02-12 06:28:19|
|Subject: Re: Parameter name standby_mode|
|Previous:||From: Fujii Masao||Date: 2010-02-12 05:38:32|
|Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL|