From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Logging from multiple connections |
Date: | 2005-11-24 02:34:36 |
Message-ID: | 438526BC.7080406@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Oliver Jowett wrote:
> Kevin Grittner wrote:
>
>> Wading through loglevel=2 output today, it occurred to me that it would
>> be nice if the jdbc log file included a prefix with something to
>> identify the connection. Sometimes you can only get an error to occur
>> on a busy system with multiple active connections, and the jdbc log
>> currently mixes everything together, which can make it hard to follow.
>
>
> Yes, this is on my todo list..
>
> The simplest way to do it seems to be to just have a static driver-wide
> counter to assign IDs to connections.
I just committed something like this to CVS HEAD -- loglevel is now
handled per connection (previously it was effectively driver-wide,
despite being specified as part of the connection URL), and logging
output now has both a connection ID and timestamp on each line.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-11-24 05:00:11 | Re: Can PostgreSQL do data type automated casting in |
Previous Message | Oliver Jowett | 2005-11-23 23:50:15 | Re: Why is bool == java.sql.Types.BIT ?? |