Re: Slowness of extended protocol

Поиск
Список
Период
Сортировка
От Tatsuo Ishii
Тема Re: Slowness of extended protocol
Дата
Msg-id 20160819.150241.1712095925015012241.t-ishii@sraoss.co.jp
обсуждение исходный текст
Ответ на Re: Slowness of extended protocol  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Ответы Re: Slowness of extended protocol  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Список pgsql-hackers
BTW, there seem to be a room to enhance JDBC driver performance. In my
understanding it always uses unnamed portal even if the SQL is like
"BEGIN" or "COMMIT" (no parameters). They are too often used. Why not
doing like this?

Prepare(stmt=S1,query="BEGIN")
Bind(stmt=S1,portal=P1)
Execute(portal=P1)
:
:
Execute(portal=P1)
:
:
Execute(portal=P1)

Instead of:

Prepare(stmt=S1,query="BEGIN")
Bind(stmt=S1,portal=null)
Execute(portal=null)
:
:
Bind(stmt=s1,portal=null)
Execute(portal=null)
:
:
Bind(stmt=s1,portal=null)
Execute(portal=null)

This way, we could save bunch of Bind messages.

I don't know what other drivers do though.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: pg_basebackup wish list
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Should we cacheline align PGXACT?