Skip site navigation (1) Skip section navigation (2)

Re: postgres 9 streaming replication

From: Alex Lai <alai(at)sesda2(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: "Khadtare, Sharad" <sharad(dot)khadtare(at)teamaol(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: postgres 9 streaming replication
Date: 2011-03-25 15:34:20
Message-ID: 4D8CB5FC.6070105@sesda2.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Fujii Masao wrote:
> On Wed, Mar 23, 2011 at 9:07 PM, Alex Lai <alai(at)sesda2(dot)com> wrote:
>   
>> I have no idea why I keep getting the message:\
>>  could not connect to the primary server: FATAL:  no pg_hba.conf entry for
>> replication connection from host "slave_server_ip", user
>> "my_super_user_name"
>>     
>
> Can you connect from slave to master by the following command?
>
>     psql "replication=1" -h <slave_ip> -p 5432 -U <my_user_name>
>
> If successful, the settings in recovery.conf would be wrong.
> Otherwise, I guess that the setting in pg_hba.conf of the master would
> be wrong. Did you reload the configuration files? What happens if you
> use "all" keyword instead of specifying the real user name? What happens
> if you use "0.0.0.0/0" instead of specifying the slave's ip? You would need
> to do trial and error approach.
>
> Regards,
>
>   
After changed to all for -U in pg_hba.conf, it connected without 
problem.  Thanks for your help.

-- 
Best regards,


Alex Lai
OMI SIPS DBA ADNET Systems , Inc. 
7515 Mission Drive, 
Suite A100 Lanham, MD 20706 
301-352-4657 (phone) 
301-352-0437 (fax) 
alai(at)sesda2(dot)com


In response to

pgsql-bugs by date

Next:From: Christopher BrowneDate: 2011-03-25 15:58:46
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Previous:From: Tom LaneDate: 2011-03-25 15:30:22
Subject: Re: BUG #5950: backend terminating after altering table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group