Re: [BUGS] Re: BUG #13854: SSPI authentication failure: wrong realm name used - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [BUGS] Re: BUG #13854: SSPI authentication failure: wrong realm name used
Date
Msg-id 20160329214032.GA925857@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #13854: SSPI authentication failure: wrong realm name used  (Christian Ullrich <chris@chrullrich.net>)
Responses Re: [BUGS] Re: BUG #13854: SSPI authentication failure: wrong realm name used
List pgsql-hackers
So, it seems that ClientAuthentication() expects to raise ereport(FATAL)
in case of authentication failures.  But what's the code path that
causes that to happen if a ereport(ERROR) happens in there?  Because all
that code is pretty careful to not do ereport(ERROR) directly and
instead return STATUS_ERROR which makes ClientAuthentication do the
FATAL report.  If this doesn't matter, then isn't this whole code overly
complicated for no reason?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Christian Ullrich
Date:
Subject: Re: BUG #13854: SSPI authentication failure: wrong realm name used
Next
From: Alvaro Herrera
Date:
Subject: standby_schedule