Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Marko Kreen wrote:
>> When pooling connections where prepared statements are in use,
>> it is hard to give new client totally clean connection as
>> there may be allocated statements that give errors when
>> new client starts preparing statements again.
> Huh, didn't we have a RESET SESSION command to do just that? What about
> cursors, for example?
We don't actually *have* one, but I believe it was agreed that that is
the right API to provide. If a pooler has to remember to clear prepared
statements, GUCs, cursors, and who knows what else, it'll be perpetually
broken because there'll be something it omits.
There might be a use-case for DEALLOCATE ALL, but needs of poolers
aren't it. I'd be inclined to vote against this unless someone can
point to a better use-case.
regards, tom lane
In response to
pgsql-patches by date
|Next:||From: David Fetter||Date: 2007-03-27 18:08:44|
|Subject: Re: Arrays of Complex Types|
|Previous:||From: Bruce Momjian||Date: 2007-03-27 17:34:20|
|Subject: Re: Recalculating OldestXmin in a long-running