| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | depesz(at)depesz(dot)com, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pg(at)fastcrypt(dot)com, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, lindner(at)inuus(dot)com, "Oliver Jowett" <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org, PgBouncer <pgbouncer-general(at)pgfoundry(dot)org> |
| Subject: | Re: Prepared Statements vs. pgbouncer |
| Date: | 2007-10-02 20:22:16 |
| Message-ID: | e51f66da0710021322t5bfdba93q19fd885a64f7e27f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 10/2/07, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > So, personally I don't have time to work on the feature, but
> > I have thought a draft design that could somewhat work in the
> > context of pgbouncer. If anyone is interested to work on that,
> > contact me.
>
> Will this work correctly if you use Session mode for pgBouncer?
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.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2007-10-02 21:42:36 | Re: statement caching link on jdbc page |
| Previous Message | Josh Berkus | 2007-10-02 20:13:56 | Re: Prepared Statements vs. pgbouncer |