Re: libpq should append auth failures, not overwrite - Mailing list pgsql-hackers

From Robert Haas
Subject Re: libpq should append auth failures, not overwrite
Date
Msg-id CA+TgmoZ_uB2Zjoah98eKriH5FYQteEC-CpihhdEoFVo1whFYkA@mail.gmail.com
Whole thread Raw
In response to Re: libpq should append auth failures, not overwrite  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: libpq should append auth failures, not overwrite
List pgsql-hackers
On Wed, Aug 15, 2018 at 11:53 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Well, I'm actually not proposing to print "maximum detail", and Fabien
> is complaining about that, which makes me think maybe I've hit a happy
> medium ;-).  In particular, the proposed patches won't change behavior
> for cases where you just give one hostname or hostaddr, and I'd argue
> that that is the only case where we really have enough track record to
> be sure that people are happy with the amount of detail provided.
> As soon as you have multiple target hosts, though, the current code's
> behavior is inadequate IMO.

I'm not entirely convinced; see the example I posted before.

> Indisputably it's inconsistent, because
> some code paths will concatenate error messages and some won't, without
> any rhyme or reason that I can detect.  I think the only reason we've
> not had more complaints is that hardly anyone is using this feature yet.

I agree that inconsistency is bad as a rule.  :-)

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq should append auth failures, not overwrite
Next
From: Alvaro Herrera
Date:
Subject: Re: C99 compliance for src/port/snprintf.c