| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <pg(at)fastcrypt(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: instrumenting the driver |
| Date: | 2005-06-17 13:53:35 |
| Message-ID: | s2b28f97.059@gwmta.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
The first thing that comes to mind is to check the
DriverManager.getLogWriter() value at key points in the code. If not
null, log timing info along with other logging/tracing info. Would this
satisfy the request?
-Kevin
>>> Dave Cramer <pg(at)fastcrypt(dot)com> 06/17/05 6:59 AM >>>
There has been a request to instrument the driver for measuring timing.
One mechanism that comes to mind is to allow one listener in execute,
etc. Or to simply measure it ourselves.
Any comments?
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
ICQ #14675561
jabber davecramer(at)jabber(dot)org
ph (519 939 0336 )
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2005-06-17 13:59:31 | Re: instrumenting the driver |
| Previous Message | Dave Cramer | 2005-06-17 12:08:25 | compatibility patch status |