From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bug w/ cursors and savepoints |
Date: | 2005-01-25 08:20:02 |
Message-ID: | 670.1106641202@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Neil Conway <neilc(at)samurai(dot)com> writes:
> On Tue, 2005-01-25 at 02:40 -0500, Tom Lane wrote:
>> Offhand I'd say this should draw a "no such cursor as foo" error.
>> I'm too tired to look into why foo still exists after the rollback...
> I'm confused; I wasn't involved in the design discussions about portals
> and subtransactions this summer, but my understanding is that making
> portals non-transactional was the conclusion. Shouldn't that imply that
> a DECLARE in an aborted subtransaction should persist?
I don't recall the discussions from last summer in detail, but it can't
possibly be rational to allow a cursor created in a failed
subtransaction to persist beyond that subtransaction... your example
in which the cursor uses tables that no longer exist is a fairly
egregious example of why not, but there are others.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2005-01-25 09:06:23 | WAL: O_DIRECT and multipage-writer |
Previous Message | Neil Conway | 2005-01-25 08:13:45 | Re: bug w/ cursors and savepoints |