Re: Parse more than bind and execute when connect to database by jdbc
От | wangshuo@highgo.com.cn |
---|---|
Тема | Re: Parse more than bind and execute when connect to database by jdbc |
Дата | |
Msg-id | df7d2551ffeacc955c5ba7bbddb28968@highgo.com.cn обсуждение исходный текст |
Ответ на | Re: Parse more than bind and execute when connect to database by jdbc (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On 2013-11-18 11:39, Amit Kapila wrote: > 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? > Thanks for your reply. This is the Log/Debug messages. Some configuration options are as follows: log_min_duration_statement = 0' log_statement = 'all' log_line_prefix = '%t [%p]: [%l-1] db=%d,user=%u [%x]' logging_collector = on >> 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 do agree with you. But I don't know what query can call parse multiple times. Could you give me more information or example about this case? Wang Shuo HighGo Software Co.,Ltd. November 18, 2013
В списке pgsql-hackers по дате отправления: