X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6B0F7D1CA15 for ; Wed, 28 Jul 2004 00:47:12 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17678-09 for ; Wed, 28 Jul 2004 03:47:08 +0000 (GMT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 95AB9D1DA75 for ; Wed, 28 Jul 2004 00:25:41 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by www.postgresql.com (Postfix) with ESMTP id D5CE0CF4AEF for ; Tue, 27 Jul 2004 12:41:22 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6RFe73E029559; Tue, 27 Jul 2004 11:40:07 -0400 (EDT) To: "Merlin Moncure" Cc: pgsql-performance@postgresql.org Subject: Re: best way to fetch next/prev record based on index In-reply-to: <29487.1090942399@sss.pgh.pa.us> References: <6EE64EF3AB31D5448D0007DD34EEB34101AEFA@Herge.rcsinc.local> <29487.1090942399@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Tue, 27 Jul 2004 11:33:19 -0400" Date: Tue, 27 Jul 2004 11:40:07 -0400 Message-ID: <29558.1090942807@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/205 X-Sequence-Number: 7596 Tom Lane writes: > "Merlin Moncure" writes: >> Plus, your where clause does not guarantee results. > No, but in combination with the ORDER BY it does. Oh, wait, you're right --- I'm mis-visualizing the situation. Hmm, it sure seems like there ought to be an easy way to do this... regards, tom lane