Re: Log files cluttered with jdbc3/4 for pg8.2

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: <mario(dot)splivalo(at)mobart(dot)hr>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Log files cluttered with jdbc3/4 for pg8.2
Date: 2007-06-23 11:33:30
Message-ID: 87y7iaaos5.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

"Mario Splivalo" <mario(dot)splivalo(at)mobart(dot)hr> writes:

> 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?

Uhm, they are "every call from the jdbc to the postgresql".

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2007-06-23 15:51:40 Re: Error reporting issue in SimpleParameterList
Previous Message Tom Lane 2007-06-22 22:05:52 Re: [JDBC] creating temporary table PostgreSql 8.1 and iBatis 2.3