Re: [Pgbouncer-general] Prepared Statements vs. pgbouncer

Поиск
Список
Период
Сортировка
От Marko Kreen
Тема Re: [Pgbouncer-general] Prepared Statements vs. pgbouncer
Дата
Msg-id e51f66da0710040918xdecee91r38eb7567a4874b@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Prepared Statements vs. pgbouncer  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-jdbc
On 10/4/07, Josh Berkus <josh@agliodbs.com> wrote:
> > Yes, then you don't need any support from pgbouncer, only
> > a way to drop all prepared plans on session end, which unfortunately
> > is available only in 8.3 - DEALLOCATE ALL / DISCARD ALL.
>
> Oh.  So on 8.2, this is still an issue becuase the plans will persist beyond
> JDBC dropping the connection?

Yes.  JDBC could avoid it by carefully dropping all plans before
closing the connection.

> Also, are you saying that on 8.3 the client
> code will have to manually issue DEALLOCATE ALL on session end?

No, it is pgbouncer's job.  Set server_reset_query to
"DISCARD ALL".  Although that happens to be available only
in 1.1 branch of pgbouncer, which should be released any day now.

In 1.0 it can be done by server_check_query = "..", server_check_delay = 0
but that makes it unusable for it's intended purpose.

--
marko

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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Prepared Statements vs. pgbouncer
Следующее
От: Guy Rouillier
Дата:
Сообщение: Re: Connection pooling