| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Florian Wunderlich <fwunderlich(at)devbrain(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: persistent portals/cursors (between transactions) |
| Date: | 2002-01-25 04:32:49 |
| Message-ID: | 200201250432.g0P4Wng10381@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> I forgot to mention that I'd like to implement a cross
> >> transaction insensitive(and read-only) cursors which
> >> any proper dbms seems to have the functionality.
>
> > That is a good idea, especially read-only, that will not require any
> > locks.
>
> If it's not holding any locks, I can guarantee you it's not insensitive.
> Consider VACUUM, or even DROP TABLE.
I assumed it would be an in-memory copy of the cursor, like a portal
that doesn't go away on transaction exit.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2002-01-25 05:18:11 | Re: persistent portals/cursors (between transactions) |
| Previous Message | Tom Lane | 2002-01-25 04:22:24 | Re: persistent portals/cursors (between transactions) |