X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6C5EC9DCA38 for ; Sat, 14 Jan 2006 14:10:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20682-01 for ; Sat, 14 Jan 2006 14:10:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 5D4AA9DC9FA for ; Sat, 14 Jan 2006 14:10:28 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0EIASCa020703; Sat, 14 Jan 2006 13:10:28 -0500 (EST) To: "Bernard Dhooghe" cc: pgsql-performance@postgresql.org Subject: Re: >= forces row compare and not index elements compare when possible In-reply-to: <1136826602.613297.42010@f14g2000cwb.googlegroups.com> References: <1136826602.613297.42010@f14g2000cwb.googlegroups.com> Comments: In-reply-to "Bernard Dhooghe" message dated "09 Jan 2006 09:10:02 -0800" Date: Sat, 14 Jan 2006 13:10:28 -0500 Message-ID: <20702.1137262228@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.088 required=5 tests=[AWL=0.088] X-Spam-Score: 0.088 X-Spam-Level: X-Archive-Number: 200601/187 X-Sequence-Number: 16665 "Bernard Dhooghe" writes: > So >= (or <=) is not optimized against an index where it could be. Work in progress... regards, tom lane