Re: Log files cluttered with jdbc3/4 for pg8.2 - Mailing list pgsql-jdbc

From Mario Splivalo
Subject Re: Log files cluttered with jdbc3/4 for pg8.2
Date
Msg-id 1182518494.16014.15.camel@localhost.localdomain
Whole thread Raw
In response to Re: Log files cluttered with jdbc3/4 for pg8.2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Log files cluttered with jdbc3/4 for pg8.2
Re: Log files cluttered with jdbc3/4 for pg8.2
List pgsql-jdbc
On Wed, 2007-06-20 at 11:16 -0400, Tom Lane wrote:
> Mario Splivalo <mario.splivalo@mobart.hr> writes:
> > I finaly see the actuall parametars the function was called with, but, I
> > have too much lines for a simple SELECT.
>
> Well, if you set log_min_messages to DEBUG, as you evidently have,
> you're going to get a pretty chatty log.  You might want to rethink
> your log_duration threshold as well.

Yes, I have log_min_messages to DEBUG, but if I set it to INFO, NOTICE,
WARNING or ERROR I still have PARSE LOG, BIND LOG/BIND DETAIL entries. I
haven't been able to found what exactley they are, and I'd realy like to
not have them in my log files.

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.

I guess I'll be using pg7.4 JDBC driver for development, and use 8.2
JDBC in production (there I have log_duration set to around 600).

Could anyone point me on what exactly PARSE LOG and BIND LOG entries
are?

    Mario


pgsql-jdbc by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: [GENERAL] standard LOB support
Next
From: Tom Lane
Date:
Subject: Re: Log files cluttered with jdbc3/4 for pg8.2