Re: DEALLOCATE ALL

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?

> I did it slightly hacky way - if DeallocateStmt->name is
> NULL is signifies DEALLOCATE ALL command.  All the code
> that looks into DeallocateStmt seems to survive the situation
> so it should be problem.  If still a new node is needed
> or additional field in the node I can rework the patch.

Wouldn't it be easier to just add a bool to DeallocateStmt?

--
Alvaro Herrera                                http://www.PlanetPostgreSQL.org
"Si un desconocido se acerca y te regala un CD de Ubuntu ...
                                     Eso es ...  Eau de Tux"