From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Better detail logging for password auth failures |
Date: | 2015-12-30 13:17:24 |
Message-ID: | CAB7nPqTNbTCLLcnf5-f9U76dhXMXmpdm9UYg6OXCDKrVbsm56A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 30, 2015 at 1:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We often tell people to look in the postmaster log for more information
> about authentication problems; but an off-list question prompted me to
> notice that many of the common authentication failure cases don't actually
> get any useful commentary in the log. The attached proposed patch
> remedies this by adding specific log detail messages for all the
> non-out-of-memory cases processed by md5_crypt_verify(). Essentially,
> this is just covering cases that I omitted to cover in commit 64e43c59,
> for reasons that no longer seem very good to me.
>
> Any objections?
Not really. +1. And the patch looks good.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-12-30 13:48:27 | Re: Better detail logging for password auth failures |
Previous Message | Aleksander Alekseev | 2015-12-30 13:01:37 | Re: Patch: fix lock contention for HASHHDR.mutex |