From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
Cc: | Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Prepared statements, parameters and logging |
Date: | 2007-06-25 10:54:04 |
Message-ID: | 6A182763-97EC-43C9-BD13-EE5375A83AC2@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Csaba,
They will all be prepared. The threshold is whether to re-use the
prepared statement.
What you are seeing is the use of unnamed statements.
If you really want them turned off use protocolVersion=2
Dave
On 25-Jun-07, at 6:47 AM, Csaba Nagy wrote:
> Hi all,
>
> I have a system (postgres 8.1) which was until now running with JDBC
> parameter prepareThreshold=1 so it is always using server side
> prepares
> (we had some trouble in the past if not setting it so). Now we are
> prepared to set this to 0, meaning no server side prepares by
> default...
>
> The problem is that I did the switch and I still see queries which are
> presumably server side prepared (marked with <unnamed> in the log - I
> enabled reporting queries longer than 2 seconds)...
>
> The question is how do I tell for sure from the DB log if a query is
> server side prepared or not ? I was presuming that <unnamed> in the
> log
> means server side prepare, some name like 'C_xyz' means client side
> prepared statement. Is this correct ?
>
> Thanks,
> Csaba.
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2007-06-25 11:13:39 | Re: Prepared statements, parameters and logging |
Previous Message | Csaba Nagy | 2007-06-25 10:47:29 | Prepared statements, parameters and logging |