| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Christian Ullrich <chris(at)chrullrich(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [HACKERS] BUG #13854: SSPI authentication failure: wrong realm name used |
| Date: | 2016-03-30 01:09:04 |
| Message-ID: | 4293.1459300144@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> Anyway, as things stand, elog(ERROR) will abort the session safely but
>> you won't necessarily get the kind of logging you want, so expected
>> auth-failure cases should try to go the STATUS_ERROR route.
> In other words, the use of palloc() and friends (psprintf in the patch)
> should be acceptable here.
Sure, no problem with that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jarosław Stokłosa | 2016-03-30 06:55:15 | Re: BUG #14046: Bad mathematical rules for 0 cast |
| Previous Message | Alvaro Herrera | 2016-03-29 22:14:13 | Re: Re: [HACKERS] BUG #13854: SSPI authentication failure: wrong realm name used |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-30 01:13:36 | Re: [COMMITTERS] pgsql: Allow to_timestamp(float8) to convert float infinity to timestam |
| Previous Message | Tomas Vondra | 2016-03-30 01:02:51 | Re: Using quicksort for every external sort run |