From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "John DeSoi *EXTERN*" <desoi(at)pgedit(dot)com>, "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: streaming replication not working |
Date: | 2013-09-24 10:48:09 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17C23AAF@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John DeSoi wrote:
> 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
You should set the same parameters on the primary, else it won't work.
> 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?
No, that shouldn't be necessary.
What are the messages in the secondary's log
after you start it?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | John DeSoi | 2013-09-24 13:59:57 | Re: streaming replication not working |
Previous Message | sachin kotwal | 2013-09-24 09:42:50 | Re: Problems with vacuum |