Re: Prepared Statements vs. pgbouncer

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Cc: PgBouncer <pgbouncer-general(at)pgfoundry(dot)org>
Subject: Re: Prepared Statements vs. pgbouncer
Date: 2007-10-04 15:46:06
Message-ID: 200710040846.06394.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Marko,

> 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? Also, are you saying that on 8.3 the client
code will have to manually issue DEALLOCATE ALL on session end?

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Marko Kreen 2007-10-04 16:18:53 Re: [Pgbouncer-general] Prepared Statements vs. pgbouncer
Previous Message Dave Cramer 2007-10-04 11:30:33 Re: Connection pooling