Re: WITH HOLD and pooled connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WITH HOLD and pooled connections
Date: 2003-08-08 21:33:58
Message-ID: 878.1060378438@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Prepared statements would be just as much of a problem. I think the
>> correct answer is simply "don't use those features in a pooled
>> environment".

> Ouch. Double ouch in fact. I'm using prepared statements extensively in
> my current (pooled conn) app. All pure selects.
> Can this be narrowed down a bit? Is it a problem on all query types?

The point is just that there's no infrastructure to manage prepared
statements, eg for a thread to discover whether someone has already
prepped a particular statement on the current connection. Evidently
you have set things up so that you don't need to do that. Panic not.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-08-08 21:34:32 pgindent run
Previous Message Bruce Momjian 2003-08-08 21:24:25 Re: contrib/vacuumlo problem in cvs