X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 873F5D8B78 for ; Mon, 12 Sep 2005 11:26:53 -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 44864-06 for ; Mon, 12 Sep 2005 14:26:46 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 8BF58D8B6C for ; Mon, 12 Sep 2005 11:26:45 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j8CEQlk9043172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Sep 2005 08:26:50 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j8CEQlxf034732 for ; Mon, 12 Sep 2005 08:26:47 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j8CEQlgw034731 for pgsql-docs@postgresql.org; Mon, 12 Sep 2005 08:26:47 -0600 (MDT) (envelope-from mfuhr) Date: Mon, 12 Sep 2005 08:26:47 -0600 From: Michael Fuhr To: pgsql-docs@postgresql.org Subject: Multicolumn index doc out of date? Message-ID: <20050912142647.GA34685@winnie.fuhr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200509/20 X-Sequence-Number: 3206 The 8.1 Release Notes have the following item: * Allow non-consecutive index columns to be used in a multi-column index So isn't the following paragraph from "Multicolumn Indexes" out of date? The query planner can use a multicolumn index for queries that involve the leftmost column in the index definition plus any number of columns listed to the right of it, without a gap. For example, an index on (a, b, c) can be used in queries involving all of a, b, and c, or in queries involving both a and b, or in queries involving only a, but not in other combinations. (In a query involving a and c the planner could choose to use the index for a, while treating c like an ordinary unindexed column.) http://developer.postgresql.org/docs/postgres/indexes-multicolumn.html -- Michael Fuhr