Re: Parse more than bind and execute when connect to database by jdbc - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parse more than bind and execute when connect to database by jdbc
Date
Msg-id CAA4eK1+FDe9V0B2Ue15=+QQc=L49LP0gP33S2NE7q9KqM=yzWw@mail.gmail.com
Whole thread Raw
In response to Parse more than bind and execute when connect to database by jdbc  (wangshuo@highgo.com.cn)
Responses Re: Parse more than bind and execute when connect to database by jdbc  (wangshuo@highgo.com.cn)
List pgsql-hackers
On Mon, Nov 18, 2013 at 7:32 AM,  <wangshuo@highgo.com.cn> wrote:
> Hi hackers,
>
>             I used jdbc to connect to PostgreSQL ,and I found parse nearly three
>             times of bind and execute.Is is normaly?   Actually bind and execute should be more than parse. Have you
confirmed that by enabling Log/Debug messages on server or you are
referring to JDBC log?

> What factors may cause this result?
I am really not sure of JDBC, but from Libpq or general concept wise,
it can happen only if someone does call parse multiple times, but then
execute only few of the statements. I think you might need to narrow
down the problem by having less number of queries in your JDBC
application. If possible start by having only 1 or 2 queries and then
see how many times parse,bind,execute gets called.


>             The OS is CentOS 5. The PG is 9.0.9. The JDBC is 9.2.
>


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UNNEST with multiple args, and TABLE with multiple funcs
Next
From: Peter Eisentraut
Date:
Subject: Re: WITHIN GROUP patch