Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: 2 forks for md5?
- 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: Sat, 24 Sep 2005 15:14:03 -0400
- Message-id: <4335A57B(dot)8000309(at)dunslane(dot)net>
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
- Follow-Ups:
- Re: 2 forks for md5?
- From: Bruce Momjian
- Re: 2 forks for md5?
- References:
- Re: 2 forks for md5?
- From: Bruce Momjian
- Re: 2 forks for md5?
- Prev by Date: Re: Proposed patch to clean up signed-ness warnings
- Next by Date: Re: 64-bit API for large objects
- Previous by thread: Re: 2 forks for md5?
- Next by thread: Re: 2 forks for md5?
- Indexes: