2

I have Postgres replication (master & slave).

The slave server has 2 local IP addresses (192.168.1.17 & 192.168.2.12). As far as I know the streaming replication worked fine with slave using 192.168.2.12. But somehow the slave could not connect to master because it required another IP:

2017-01-30 23:53:13.510 WIB >FATAL: no pg_hba.conf entry for replication connection from host "192.168.1.17", user "user1", SSL off

I can put 192.168.1.17 in pg_hba.conf to work around this problem. I want to know if I did anything wrong to make the slave Postgres IP change? It was working just fine.

closed as unclear what you're asking by dezso, Philᵀᴹ, RLF, LowlyDBA, Kin Shah Feb 7 '17 at 19:47

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • How is the connection specified in recovery.conf? – dezso Jan 31 '17 at 9:18
0

This is not the question about PostgreSQL - this is about routing. Just route from 192.168.1.17 became as better than from 192.168.2.12

Not the answer you're looking for? Browse other questions tagged or ask your own question.