On 22/06/10 01:49, Heikki Linnakangas wrote:
> On 22/06/10 00:47, Heikki Linnakangas wrote:
>> 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.
>
> Like this.
>
> (I'll need to revert the broken commit before applying this)
Ok, here's my final patch for this that I'll commit shortly. I added a
new boolean for the "pinned" status in the end, rather than confuse it
with the portal status. It's simpler that way.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com