From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: MOVE LAST: why?
Date: Wed, 08 Jan 2003 17:42:26 -0500
Message-ID: <22435.1042065746@sss.pgh.pa.us> (raw)
In-Reply-To: <3E1BEFFE.88B57516@tpf.co.jp>
References: <200301072329.h07NT2X28922@candle.pha.pa.us>
<27934.1041984327@sss.pgh.pa.us>
<3E1B9DCD.75859501@tpf.co.jp>
<501.1041997832@sss.pgh.pa.us>
<3E1BA5E6.9463718F@tpf.co.jp>
<863.1042000401@sss.pgh.pa.us>
<3E1BAFF6.B0114A67@tpf.co.jp>
<1082.1042002375@sss.pgh.pa.us>
<3E1BEFFE.88B57516@tpf.co.jp>
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> I'm suspicios if we should implement scrollable cursors
> with the combination of the current MOVE and FETCH implemen-
> tation. For example the backwards FETCH operation for group
> nodes isn't implemented properly yet(maybe).
Yeah, backwards scan is not implemented for quite a large number of plan
node types :-(. I am not sure that it is practical to fix them all.
I have been toying with the notion of making cursors on complex plans
safe for FETCH BACKWARD by sticking a MATERIAL node atop the plan, if
the top plan node isn't one that can handle backwards scan.
The trouble with this of course is that one of the main things people
like to use cursors for is huge result sets, and materializing those is
the last thing you want to do :-(
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, Inoue@tpf.co.jp, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
Subject: Re: MOVE LAST: why?
In-Reply-To: <22435.1042065746@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox