Re: Thoughts on pg_hba.conf rejection - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Thoughts on pg_hba.conf rejection
Date
Msg-id y2u603c8f071004141737kf8b19c07pc5d745f83149b3df@mail.gmail.com
Whole thread Raw
In response to Re: Thoughts on pg_hba.conf rejection  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Thoughts on pg_hba.conf rejection  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Thoughts on pg_hba.conf rejection  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Wed, Apr 14, 2010 at 8:31 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Tom Lane wrote:
>> Robert Haas <robertmhaas@gmail.com> writes:
>> > What's wrong with something like "connection not permitted" or
>> > "connection not authorized"?
>>
>> The case that we're trying to cater to with the existing wording is
>> novice DBAs, who are likely to stare at such a message and not even
>> realize that pg_hba.conf is what they need to change.  Frankly, by
>> the time anyone is using REJECT entries they are probably advanced
>> enough to not need much help from the error message; but what you
>> propose is an absolute lock to increase the number of newbie questions
>> on the lists by a large factor.
>
> Agreed.  I would rather have an inaccurate error message that mentions
> pg_hba.conf than an accurate one that doesn't.
>
> Error messages should always point at a solution, if possible.

OK, how about "connection not authorized by pg_hba.conf"?

...Robert


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Thoughts on pg_hba.conf rejection
Next
From: Bruce Momjian
Date:
Subject: Re: extended operator classes vs. type interfaces