BUG #6756: primary_conninfo is ignored if restore_command is set..
The following bug has been logged on the website:
Bug reference: 6756
Logged by: Greg Hazel
Email address: ghazel@gmail.com
PostgreSQL version: 9.1.4
Operating system: Amazon Linux
Description:
Trying to get a slave to stream updates from a master, I had both:
restore_command = 'pg_standby /data/pgsql9/archive %f %p %r 2>>standby.log'
and:
primary_conninfo = 'host=10.x.y.z port=5432 user=postgres'
This configuration never streamed from the master, even after restarts,
waiting hours, etc. After all that, I removed restore_command and restarted,
and the slave started streaming immediately.
This seems to contradict many guides and the documentation I've found.
On Wed, Jul 25, 2012 at 10:42 AM, <ghazel@gmail.com> wrote:
The following bug has been logged on the website:
Bug reference: 6756
Logged by: Greg Hazel
Email address: ghazel@gmail.com
PostgreSQL version: 9.1.4
Operating system: Amazon Linux
Description:Trying to get a slave to stream updates from a master, I had both:
restore_command = 'pg_standby /data/pgsql9/archive %f %p %r 2>>standby.log'
and:
primary_conninfo = 'host=10.x.y.z port=5432 user=postgres'
This configuration never streamed from the master, even after restarts,
waiting hours, etc. After all that, I removed restore_command and restarted,
and the slave started streaming immediately.This seems to contradict many guides and the documentation I've found.
No. You need to use cp or something instead of pg_standby if you'd like to
use streaming replication. pg_standby is the tool for file-based log shipping
replication.
Regards,
--
Fujii Masao