| 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-23 23:28:38 |
| Message-ID: | 4384FB26.1020902@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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 considered backend PID, but that could in theory be duplicated, and
you can always match up PID to connection ID from the initial connection
setup logging.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2005-11-23 23:41:03 | Re: Why is bool == java.sql.Types.BIT ?? |
| Previous Message | Oliver Jowett | 2005-11-23 23:22:46 | Re: Room to optimize updates through ResultSet |