Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections
Date
Msg-id BANLkTin88sBQPSmFV+kWtquwbLGhdB3TjQ@mail.gmail.com
Whole thread Raw
In response to Bug in pg_hba.conf or pg_basebackup concerning replication connections  (Joshua Berkus <josh@agliodbs.com>)
Responses Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections  (Josh Berkus <josh@agliodbs.com>)
Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 10 April 2011 04:23, Joshua Berkus <josh@agliodbs.com> wrote:
> If I have the following line in pg_hba.conf:
>
> host    replication     replication             all                     md5
>
> pg_basebackup -x -v -P -h master1 -U replication -D $PGDATA
> pg_basebackup: could not connect to server: FATAL:  no pg_hba.conf entry for replication connection from host
"216.121.61.233",user "replication" 
>

Welcome to the wonderful world of keywords in hba not being specific
to fields.  I encountered this problem myself back in Oct 2010 [1] and
predicted that it would bite other users.  You've been kind enough to
validate that prediction.  I submitted a WIP patch aimed at fixing it
just over a week ago [2].

Until that patch (or some other solution) goes through, you'll need to
quote "replication" in your hba.conf if you want to use it as a
username.

Cheers,
BJ

[1] http://archives.postgresql.org/message-id/AANLkTi=q8DZj79OKrWc-kE9zg-rH-1tcQdqbsbKfO1zF@mail.gmail.com
[2] http://archives.postgresql.org/message-id/AANLkTin8p0SoN1YJeXO3cgiDLxev67oh4c7VtJ7e0h4O@mail.gmail.com


pgsql-hackers by date:

Previous
From: Jesper Krogh
Date:
Subject: Re: Evaluation of secondary sort key.
Next
From: Peter Eisentraut
Date:
Subject: Re: \dO versus collations for other encodings