I’m using pg 9.1.3 on CentOS 5 and have a few slave databases setup
using the built in streaming replication.
On the slaves I set the “listen_addresses” config option to an ip
address for a virtual alias on my network interfaces. The host has an
address of 10.1.1.10, and there is a virtual alias of 10.1.1.40 that
the slave postmaster binds to.
When the slave makes it connection to the master to start replication
the source address for the connection is the host address, not the
virtual alias address. Connections appear to come from 10.1.1.10,
instead of the slave postmaster address of 10.1.1.40.
This seems like a bug to me. I could understand that if the
postmaster is listening on all interfaces, then it should use whatever
the IP is for the for the host, but in an instance where the
postmaster has been configured to listen to a specific address it
seems like the call to start the replication should be passed that
address so connections come from the slave postmaster’s IP, instead of
Is there a config option that can be used to adjust this? I've looked
in the docs, but haven't found one yet.
Is this perhaps a bug, or lack of feature?
|How to improve my slow query for table have list of child table?||3|
|Unintuitive behavior regarding inheritance||5|
|Schema Archive cant find table||4|
|Tuning / performance questions||3|
|pg_upgrade and statistics generation||0|
|Pgfoundry problem with Npgsql bug tracker||0|
|problems sending email to list||1|
|Dynamic File Name for COPY TO in Stored Procedure||2|
|Re: Getting FATAL: terminating connection due to administrator command||2|