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

From Andrew Dunstan
Subject Re: 2 forks for md5?
Date
Msg-id 1141.24.211.165.134.1127427208.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: 2 forks for md5?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 2 forks for md5?
List pgsql-hackers
Tom Lane said:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> I turned on passwords and did see duplicate connections:
>
>>     LOG:  connection received: host=[local]
>>     LOG:  connection received: host=[local]
>>     LOG:  connection authorized: user=postgres database=test
>>     LOG:  disconnection: session time: 0:00:00.61 user=postgres
>>     database=test host=[local]
>

>
> One answer is to downgrade the "connection received" to a DEBUGn
> message, so that it's only seen by those who presumably have something
> of a clue.  I don't really care for this, but you could certainly argue
> that the other messages are sufficient for normal purposes.


Why not INFO?

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 2 forks for md5?
Next
From: Tatsuo Ishii
Date:
Subject: Re: Proposed patch to clean up signed-ness warnings