On Fri, Feb 12, 2010 at 4:59 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Joachim Wieland wrote: >> On Fri, Feb 12, 2010 at 7:28 AM, Fujii Masao <masao.fu...@gmail.com> wrote: >>> 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. >> >> On the other hand, if it has to use defaults for the target host/port, >> chances are high that either it connects to the wrong host/port or >> that SR is just not wanted :-) > > Agreed. I've changed it now so that if primary_conninfo is not set, it > doesn't try to establish a streaming connection. If you want to get the > connection information from environment variables, you can use > primary_conninfo=''.
If standby_mode is enabled, and neither primary_conninfo nor restore_command are set, the standby would get stuck. How about forbidding (i.e., causing a FATAL message) this wrong setting? 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
