Re: persistent portals/cursors (between transactions)

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Florian Wunderlich <fwunderlich(at)devbrain(dot)de>, pgsql-general(at)postgresql(dot)org
Subject: Re: persistent portals/cursors (between transactions)
Date: 2002-01-25 07:45:40
Message-ID: 3C510D24.8E1FDF7F@tpf.co.jp
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.

It's already possible to keep a lock accross transactions.
So it would keep an AccessShareLock across transactions.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Florian Wunderlich 2002-01-25 13:01:45 Re: persistent portals/cursors (between transactions)
Previous Message Jan Wieck 2002-01-25 05:18:11 Re: persistent portals/cursors (between transactions)