Re: Better detail logging for password auth failures - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Better detail logging for password auth failures
Date
Msg-id 20151230134827.mcgvr45ybyqabdmc@alap3.anarazel.de
Whole thread Raw
In response to Better detail logging for password auth failures  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Better detail logging for password auth failures
List pgsql-hackers
On 2015-12-29 11:07:26 -0500, Tom Lane wrote:
> In passing, the patch gets rid of a vestigial CHECK_FOR_INTERRUPTS()
> call; it was added by e710b65c and IMO should have been removed again
> by 6647248e.  There's certainly no very good reason to have one right
> at that spot anymore.

Why? Doesn't seem like the worst place for an explicit interrupt check?
I think we don't really have a problem with too many such checks... We
surely could move it, but I don't really see how it's related to the
topic at hand nor do I think it's really worth pondering about
extensively.

Andres



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Better detail logging for password auth failures
Next
From: Alvaro Herrera
Date:
Subject: Re: Making tab-complete.c easier to maintain