| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, Kyotaro HORIGUCHI <kyota(dot)horiguchi(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logging of PAM Authentication Failure |
| Date: | 2013-05-17 00:16:57 |
| Message-ID: | CA+TgmobHaQUB0booOOfBzdtjSOsVFqp45TGA47mb5HOnH4uEYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 16, 2013 at 7:01 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> I unfortunately have to say I don't really see the point of this. The
> cost of the additional connection attempt is rather low and we have to
> deal with the superflous attempts anyway since there will be old libpqs
> around for years. Why is this worth the effort?
I have always considered this a wart, and I think we've had customers
complain about these kinds of things, too. So +1 from me for fixing
it. If not everyone updates their client to take advantage of the new
APIs, so be it. If psql and pgAdmin do, it'll solve 90% of the
problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | amul sul | 2013-05-17 00:22:40 | Proposal to add connection request Wait-time in PSQL client. |
| Previous Message | Robert Haas | 2013-05-17 00:12:27 | Re: BUG #8167: false EINVAL -22 for opening a file |