| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | tony(dot)locke(at)wessexwater(dot)co(dot)uk |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #11204: Log reason for authentication failure |
| Date: | 2014-08-18 14:19:07 |
| Message-ID: | 18413.1408371547@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
tony(dot)locke(at)wessexwater(dot)co(dot)uk writes:
> The following bug has been logged on the website:
> Bug reference: 11204
> Logged by: Tony Locke
> Email address: tony(dot)locke(at)wessexwater(dot)co(dot)uk
> PostgreSQL version: 9.2.9
> Operating system: Windows Server 2008
> Description:
> Hi, recently I couldn't work out why a user couldn't log in, and it turned
> out that their role had expired. In the log, postgres merely said that the
> log in had failed, but didn't give the reason. It would be really good if it
> said in the log that it failed because the role had expired.
Already done for 9.4 and later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Locke | 2014-08-18 14:27:50 | Re: BUG #11204: Log reason for authentication failure |
| Previous Message | Tom Lane | 2014-08-18 14:14:08 | Re: Re: BUG #11178: JSONB : The NOT operator applies to the <@ operator, even after casting to ::bool |