Re: Parameter name standby_mode
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Joachim Wieland <joe@mcknight.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-02-12T06:19:34Z
Lists: pgsql-hackers
Fujii Masao wrote: > On Wed, Feb 10, 2010 at 8:16 PM, Heikki Linnakangas > <heikki.linnakangas@enterprisedb.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. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com