Re: Logging failed sql commands trough jdbc? - Mailing list pgsql-jdbc

From Guillaume Smet
Subject Re: Logging failed sql commands trough jdbc?
Date
Msg-id 1d4e0c10702190730p718eb535ic9cc6ee7c8115989@mail.gmail.com
Whole thread Raw
In response to Logging failed sql commands trough jdbc?  (Mario Splivalo <mario.splivalo@mobart.hr>)
List pgsql-jdbc
Hi Mario,

On 2/19/07, Mario Splivalo <mario.splivalo@mobart.hr> wrote:
> I'm using pg74.215.jdbc3.jar  with PostgreSQL 8.1.2. I'm not using jdbc
> driver for postgres 8 because of prepared transactions wich makes my
> postgres log file look like this:
> 2007-02-19 15:02:51.299 CET [32228] <testDb> SELECTLOG:  duration:
> 2481.387 ms  statement: EXECUTE <unnamed>  [PREPARE:  select * from
> update_message_status($1, $2, $3, $4, $5, $6, $7) as result]

In fact, you can use 8.1 driver with ?protocolVersion=2.

> Is there a way to force postgres to display those parameters, or to
> force JDBC to log all the queries sent to postgres? Even better, can
> postgres show the parametars in the 'SELECTCONTEXT' line above (instead
> of $1, $2, $3?) I don't need prepared transactions for production
> (although I'm not sure about the speed improvement - not that my test
> were accurate).

If you can plan a migration to PostgreSQL 8.2, values of the
parameters are now logged so it should solve your problem.

--
Guillaume

pgsql-jdbc by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: query using JDBC with postgresql
Next
From: Kris Jurka
Date:
Subject: Re: NPE in BlobInputStream