From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WITH HOLD and pooled connections |
Date: | 2003-08-08 20:25:37 |
Message-ID: | 200308082025.h78KPb211756@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
TODO item?
---------------------------------------------------------------------------
Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > On Fri, 2003-08-08 at 16:00, Tom Lane wrote:
> >> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >>> Seems we have a problem with pooled connections and WITH HOLD cursors.
> >>> We have code to reset transaction state and variables via RESET ALL, but
> >>> how do we remove WITH HOLD cursors when we pass a connection to a new
> >>> client?
> >>
> >> 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".
>
> > Actually, prepared statements in a pooled environment would be very
> > useful if you could ask what the currently prepared names for that
> > connection are.
>
> Hm. Good thought. Maybe the same is true of held cursors.
>
> It would be a simple addition at either the protocol or SQL level to
> list the names of existing prepared statements and portals. Probably
> too late for 7.4 though.
>
> regards, tom lane
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-08 20:28:14 | Re: WITH HOLD and pooled connections |
Previous Message | Tom Lane | 2003-08-08 20:24:04 | Re: WITH HOLD and pooled connections |