Re: Prepared Statements vs. pgbouncer - Mailing list pgsql-jdbc

From Josh Berkus
Subject Re: Prepared Statements vs. pgbouncer
Date
Msg-id 200710040846.06394.josh@agliodbs.com
Whole thread Raw
In response to Re: Prepared Statements vs. pgbouncer  ("Marko Kreen" <markokr@gmail.com>)
Responses Re: [Pgbouncer-general] Prepared Statements vs. pgbouncer  ("Marko Kreen" <markokr@gmail.com>)
List 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

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Connection pooling
Next
From: "Marko Kreen"
Date:
Subject: Re: [Pgbouncer-general] Prepared Statements vs. pgbouncer