Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug in pg_hba.conf or pg_basebackup concerning replication connections
Date: 2011-04-09 19:18:30
Message-ID: BANLkTin88sBQPSmFV+kWtquwbLGhdB3TjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10 April 2011 04:23, Joshua Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-04-09 21:22:23 Re: \dO versus collations for other encodings
Previous Message Jesper Krogh 2011-04-09 19:05:50 Re: Evaluation of secondary sort key.