X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9213ED1B4E1 for ; Tue, 11 Nov 2003 00:42:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 22925-02 for ; Mon, 10 Nov 2003 20:41:40 -0400 (AST) Received: from web21407.mail.yahoo.com (web21407.mail.yahoo.com [216.136.232.77]) by svr1.postgresql.org (Postfix) with SMTP id 5E571D1B50B for ; Mon, 10 Nov 2003 20:41:36 -0400 (AST) Message-ID: <20031111004139.47333.qmail@web21407.mail.yahoo.com> Received: from [64.81.205.234] by web21407.mail.yahoo.com via HTTP; Mon, 10 Nov 2003 16:41:39 PST Date: Mon, 10 Nov 2003 16:41:39 -0800 (PST) From: ow Subject: Re: pg 7.4.rc1, Range query performance To: Stephan Szabo Cc: pgsql-sql@postgresql.org In-Reply-To: <20031108183630.I51201@megazone.bigpanda.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/102 X-Sequence-Number: 15917 --- Stephan Szabo wrote: > I'm not sure that AK_abc is the best index for check a range on a and > single values on b and c. I'd think that something like an index > on (b,c,a) would probably be better for this purpose (without doing any > testing ;) ). That would not work for us since most of the time users are working with most recent data, hence column "a" is the first in the index. Thanks __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree