| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 2 forks for md5? |
| Date: | 2005-09-24 19:14:03 |
| Message-ID: | 4335A57B.8000309@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Drake | 2005-09-24 19:47:26 | Re: 64-bit API for large objects |
| Previous Message | Tom Lane | 2005-09-24 17:13:00 | Re: Proposed patch to clean up signed-ness warnings |