Andrew Dunstan wrote: > 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?
Yea, we could do that, but does it make sense to downgrade the connection message, especially since the "connection authorized" message doesn't contain the hostname. We would have to add the host name to the "connection authorized" message and at that point there is little need for the "connection received" message. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
