Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Prepared Statements vs. pgbouncer


  • From: Gregory Stark <stark(at)enterprisedb(dot)com>
  • To: "Paul Lindner" <lindner(at)inuus(dot)com>
  • Cc: <pgsql-jdbc(at)postgresql(dot)org>
  • Subject: Re: Prepared Statements vs. pgbouncer
  • Date: Sat, 29 Sep 2007 10:36:33 +0100
  • Message-id: <87sl4xvmn2.fsf@oxford.xeocode.com> <text/plain>

"Paul Lindner" <lindner(at)inuus(dot)com> writes:

>   * pgbouncer notices that client A is idle and reassigns backend to 
>     client B

What do you mean by "notices"? 

Prepared statements are only one form of state which can persist beyond a
transaction end. I don't think you can reassign connections unless you get
some sort of explicit notice that the client is done with any state it has set
up. Either the driver supports noticing such a state because there are no
active references to its handle or the client issues a statement like RESET
ALL or something equivalent.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group