From: | Mario Splivalo <mario(dot)splivalo(at)mobart(dot)hr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Log files cluttered with jdbc3/4 for pg8.2 |
Date: | 2007-07-02 12:41:42 |
Message-ID: | 1183380102.585.14.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 2007-06-22 at 10:00 -0400, Tom Lane wrote:
> > I need to have log_duration at 0 so I log EVERY call from the jdbc to
> > the postgresql because that's excellent way of debuging the dataflow
> > from the middle-tier to the application.
>
> That is a job for log_statement not log_duration.
Thnx, that makes sense now :) I guess I overlooked log_statement for
some reason in pg8.0.
Altough I'd like to see this:
SELECT LOG: execute <unnamed>: select * from ad_get('104', '2007-07-02
14:36:57.361+02', '109')
instead of
SELECT LOG: execute <unnamed>: select * from ad_get($1, $2, $3) as
result
SELECT DETAIL: parameters: $1 = '104', $2 = '2007-07-02 14:36:57.361
+02', $3 = '109'
Yes, I know, prepared statements, but still..
Mario
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Rouillier | 2007-07-02 15:38:16 | Re: Replace usage of a table in query with its array values |
Previous Message | Loredana Curugiu | 2007-07-02 08:23:58 | Replace usage of a table in query with its array values |