| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug w/ cursors and savepoints |
| Date: | 2005-01-26 23:59:33 |
| Message-ID: | 23440.1106783973@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 Wed, 2005-01-26 at 12:02 -0300, Alvaro Herrera wrote:
>> Hmm ... not sure how hard that is.
> Would it work to record the sub XID of the deleting subtxn on CLOSE, and
> then consider whether to "really" do the deletion when the subtxn
> commits/aborts?
It'd take more than that. Consider
BEGIN;
DECLARE c CURSOR ...;
SAVEPOINT x;
CLOSE c;
DECLARE c CURSOR ...; -- draws duplicate-cursor error
You'd need to do something to "hide" the deleted cursor for the
remainder of its subtransaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-01-27 00:10:26 | Re: Data statement format used by the .sh scripts |
| Previous Message | Neil Conway | 2005-01-26 23:55:47 | Re: bug w/ cursors and savepoints |