Re: 2 forks for md5? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: 2 forks for md5?
Date
Msg-id 4335A57B.8000309@dunslane.net
Whole thread Raw
In response to Re: 2 forks for md5?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: 2 forks for md5?
List pgsql-hackers

Bruce Momjian wrote:

>Tom Lane wrote:
>  
>
>>
>>I'm coming to agree with Andrew that a documentation patch might be the
>>best answer.  But where to put it ... under the description of the
>>log_connections GUC var?
>>    
>>
>
>I am thinking we should wait for someone else to notice the double log
>entries before mentioning it in the docs.
>  
>

If I had a more Machiavellian bent I would make sure that happened ;-)

How about this note under log_connections?:

"Some clients (notably psql) sometimes try to connect without a password 
before trying with a password. This behaviour will generate two log 
lines if log_connections is turned on, even though to the user it 
appears that only one connection has occurred."

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposed patch to clean up signed-ness warnings
Next
From: Jeremy Drake
Date:
Subject: Re: 64-bit API for large objects