Re: Prepared Statements vs. pgbouncer

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pg(at)fastcrypt(dot)com
Cc: Josh Berkus <josh(at)agliodbs(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
Subject: Re: Prepared Statements vs. pgbouncer
Date: 2007-10-01 18:44:10
Message-ID: 19675.1191264250@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> Josh Berkus wrote:
>> So where is it going to be easier to fix this ... pgBouncer, or pg-JDBC?

> pgBouncer is broken so I'd fix it.

It's an enormous mistake to imagine that prepared statements are the
only issue. What about GUC settings and temp tables, to mention a
couple other bits of per-session state?

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Josh Berkus 2007-10-01 18:44:58 Re: Prepared Statements vs. pgbouncer
Previous Message Heikki Linnakangas 2007-10-01 18:39:06 Re: Prepared Statements vs. pgbouncer