Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id F3112475E31 for ; Wed, 8 Jan 2003 18:51:46 -0500 (EST) Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (Postfix) with SMTP id C254C475D3B for ; Wed, 8 Jan 2003 18:51:45 -0500 (EST) Received: (qmail 19415 invoked from network); 8 Jan 2003 23:51:47 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.tpf-fw-c.co.jp with SMTP; 8 Jan 2003 23:51:47 -0000 Received: from tpf.co.jp (3dgateway1 [126.0.1.60]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id IAA16326; Thu, 9 Jan 2003 08:51:47 +0900 (JST) Message-ID: <3E1CBA0E.8232CF23@tpf.co.jp> Date: Thu, 09 Jan 2003 08:53:50 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Tom Lane Cc: Bruce Momjian , pgsql-hackers@postgresql.org Subject: Re: MOVE LAST: why? 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> <22435.1042065746@sss.pgh.pa.us> <22682.1042067111@sss.pgh.pa.us> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/414 X-Sequence-Number: 34024 Tom Lane wrote: > > Perhaps we could do something with a hybrid technique: don't materialize > the cursor output unless user actually asks for backwards scan. Or we can check the existence of SCROLL keyword which is currently ignored. In the first place SQL standard only allows NEXT fetch unless SCROLL is specified. regards, Hiroshi Inoue http://w2422.nsk.ne.jp/~inoue/