From: | John DeSoi <desoi(at)pgedit(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org> |
Subject: | streaming replication not working |
Date: | 2013-09-23 15:20:04 |
Message-ID: | 1EB5E8BE-3992-4113-98B7-C1E23359A90F@pgedit.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a 9.2.4 (CentOS 6.5) standby that has been working with no problems using log shipping. I wanted to add streaming replication which I thought would be as simple as adding primary_conninfo to recovery.conf and restarting the standby. But on restart there is no message or error about connecting to the primary for replication. pg_stat_replication is empty on the primary and I don't see any errors on the primary either.
Here is what I have on the standby:
postgresql.conf
hot_standby = on
max_wal_senders = 2
wal_level = hot_standby
recovery.conf
standby_mode = 'on'
trigger_file = '/pgsql/9.2/data/failover.trigger'
primary_conninfo = 'host=localhost port=21333 user=postgres'
restore_command = 'pg_standby -t /pgsql/9.2/data/failover.trigger /shared/pgbackup %f %p %r'
archive_cleanup_command = 'pg_archivecleanup /shared/pgbackup %r'
I have a ssh tunnel setup on localhost and have verified the replication user can connect to the primary.
Am I missing something obvious? Do I have to back up the primary again to make this change?
Thanks,
John DeSoi, Ph.D.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2013-09-23 15:22:17 | Re: Tree structure |
Previous Message | Andrus | 2013-09-23 15:19:32 | Re: Query runs forever after upgrading to 9.3 |