Excerpts from Heikki Linnakangas's message of lun jun 21 18:29:48 -0400 2010: > On 22/06/10 00:59, Alvaro Herrera wrote: > > Excerpts from Heikki Linnakangas's message of lun jun 21 17:47:43 -0400 > > 2010: > > > >> Maybe it would be easier to somehow protect the portal then, and throw > >> an error if you try to close it. We could just mark the portal as > >> PORTAL_ACTIVE while we run the user statements, but that would also > >> forbid fetching or moving it. I'm thinking of a new "pinned" state, > >> which is like PORTAL_READY except that the portal can't be dropped like > >> in PORTAL_ACTIVE state. > > > > Why is it an error to close the portal? > > What useful behavior ẃould you expect from closing it?
I don't know; it was you who said that the current behavior mimicked Oracle. If it's not useful, then I don't have a problem with your proposal. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
