On 31 March 2011 04:53, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Mar 31, 2011 at 3:37 AM, Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com>
> > when I used the postgres login 'replication' as the account for streaming
> > replication I get the following error message:
> > 2011-03-28 18:06:47 CEST FATAL: could not connect to the primary server:
> > FATAL: no pg_hba.conf entry for replication connection from host
> > "172.16.56.122", user "replication", SSL off
> > The corresponding pg_hba.conf entry was correct and there was no other
> > matching entry before that line.
> > # TYPE DATABASE USER CIDR-ADDRESS METHOD
> > host replication replication 172.16.56.122/32
> > By changing the account name - everything worked as smoth as I am used to
> > with postgres.
> This is a constraint of streaming replication, and listed as a TODO item.
> Have pg_hba.conf consider "replication" special only in the database
> * http://archives.postgresql.org/pgsql-hackers/2010-10/msg00632.php
And Brendan was right:
I suspect this is going to trip a lot of people up. We could just
document it and tell people that if they want to use 'replication' as
a username, they'd better quote it in pg_hba.conf.
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
In response to
pgsql-admin by date
|Next:||From: bilal ghayyad||Date: 2011-03-31 11:17:32|
|Subject: ls /var/lib/pgsql/data nothing|
|Previous:||From: Uwe Bartels||Date: 2011-03-31 04:37:45|
|Subject: Re: problem with an account name 'replication' for streaming replication|