On Fri, Feb 12, 2010 at 4:04 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Fujii Masao wrote: >> On Fri, Feb 12, 2010 at 3:19 PM, Heikki Linnakangas >> <heikki.linnakan...@enterprisedb.com> wrote: >>> Fujii Masao wrote: >>>> 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. >> >> Yeah, even if primary_conninfo is not given, the standby tries to invoke >> walreceiver by using the another connection settings (environment variables >> or defaults). This is intentional behavior, and would make the setup of SR >> easier. So I'd like to leave it be. > > You could do primary_conninfo='' for that. > > Maybe we should have two options, "streaming_mode='on'" and > "primary_conninfo='...'".
It looks better for me to extend the "standby_mode": For example, standby_mode = 'streaming' or 'archive'. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
