On Sep 25, 2013, at 8:36 AM, Guillaume Lelarge <guilla...@lelarge.info> wrote:
> Your config file and your debug logs don't match. Your config file says > that the restore command is rsync, but your logs say its pg_standby. > > Check if you have a pg_standby process on the slave. That would explain > why the slave never tries to establish a replication connection to the > master. rsync is only used in the primary configuration to push the WAL files to the standby. But pg_standby is indeed the problem. I thought pg_standby was a more feature rich option than using cp for the restore command. I see now the documentation says it supports creation of a "warm standby". It did not occur to me this meant the standby could not connect to the primary for streaming replication. Even when using pg_standby, the server was really a "hot standby" because I was able to connect to it and make read-only queries. I think it would be helpful for pg_standby to emit a warning if primary_conninfo is set it the recovery.conf. I changed the restore command to use cp and now everything appears to be working as expected. Thanks very much for your help and to everyone who offered suggestions. John DeSoi, Ph.D. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
