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: Oliver Jowett <oliver(at)opencloud(dot)com>
  • To: Paul Lindner <lindner(at)inuus(dot)com>
  • Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-jdbc(at)postgresql(dot)org
  • Subject: Re: Prepared Statements vs. pgbouncer
  • Date: Sun, 30 Sep 2007 20:11:04 +1300
  • Message-id: <46FF4C08.2090608@opencloud.com> <text/plain>
Paul Lindner wrote:


2) If we try to prepare a statement with an hashed name and it already
   exists then we ignore the error and continue.


Errors will cause the current transaction to fail..


3) If we receive an error while executing a prepared statement with an
   hashed name the driver will try to re-prepare the statement and
   re-execute the query.  If an error occurs after this retry step then
   error are surfaced to the caller.


... so you can't just back off and try again.

-O
Home | Main Index | Thread Index

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