| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Bug in PL/pgSQL FOR cursor variant |
| Date: | 2010-06-21 22:49:57 |
| Message-ID: | 4C1FEC95.7090708@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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)
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| plpgsql-forc-fix-2.patch | text/x-diff | 6.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-06-21 23:50:39 | Re: [BUGS] Server crash while trying to read expression using pg_get_expr() |
| Previous Message | Heikki Linnakangas | 2010-06-21 22:29:48 | Re: Bug in PL/pgSQL FOR cursor variant |