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 E668CD1B37E for ; Wed, 28 Jul 2004 11:07:26 -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 69609-09 for ; Wed, 28 Jul 2004 14:07:09 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9D3B6D1B1E0 for ; Wed, 28 Jul 2004 11:07:04 -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 i6SE72aT021450; Wed, 28 Jul 2004 10:07:02 -0400 (EDT) To: Greg Stark Cc: Stephan Szabo , Merlin Moncure , pgsql-performance@postgresql.org Subject: Re: best way to fetch next/prev record based on index In-reply-to: <87oem0u182.fsf@stark.xeocode.com> References: <6EE64EF3AB31D5448D0007DD34EEB34101AEFF@Herge.rcsinc.local> <20040727204057.S28969@megazone.bigpanda.com> <87oem0u182.fsf@stark.xeocode.com> Comments: In-reply-to Greg Stark message dated "28 Jul 2004 01:53:17 -0400" Date: Wed, 28 Jul 2004 10:07:01 -0400 Message-ID: <21449.1091023621@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/214 X-Sequence-Number: 7605 Greg Stark writes: > Removing <,<=,>,>= would be trivial. ... and not backwards-compatible. If we did that then cases involving unlabeled row expressions would no longer work as they did in prior releases. For example select (1,2,3) < (4,5,6); is accepted by all releases back to 7.0, and probably much further (but 7.0 is the oldest I have handy to test). The only reason the code in parse_expr.c appears new is that the functionality used to be in gram.y. I'd like to see this fixed to comply with the spec, but given the lack of complaints about the existing behavior over so many years, ripping it out meanwhile doesn't seem appropriate. regards, tom lane