Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 71D41476CDF for ; Tue, 7 Jan 2003 23:33:20 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 93105476BF7 for ; Tue, 7 Jan 2003 23:33:19 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h084XL0U000864; Tue, 7 Jan 2003 23:33:21 -0500 (EST) To: Hiroshi Inoue Cc: Bruce Momjian , pgsql-hackers@postgresql.org Subject: Re: MOVE LAST: why? In-reply-to: <3E1BA5E6.9463718F@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> Comments: In-reply-to Hiroshi Inoue message dated "Wed, 08 Jan 2003 13:15:34 +0900" Date: Tue, 07 Jan 2003 23:33:21 -0500 Message-ID: <863.1042000401@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/372 X-Sequence-Number: 33982 Hiroshi Inoue writes: > Tom Lane wrote: >> Sure. FETCH n in Postgres has always corresponded to FETCH RELATIVE n. > IIRC in SQL standard FETCH retrieves rows one by one. Yes, Postgres' idea of FETCH is only weakly related to the spec's idea. But I believe you get similar results if you consider only the row last returned by our FETCH. regards, tom lane