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 DD56E3A5C0F for ; Fri, 28 Jan 2005 17:12:14 +0000 (GMT) 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 71798-04 for ; Fri, 28 Jan 2005 17:12:06 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id A30A73A5B46 for ; Fri, 28 Jan 2005 17:12:05 +0000 (GMT) Received: (qmail 21553 invoked from network); 28 Jan 2005 18:12:20 +0100 Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2) by boutiquenumerique.com with SMTP; 28 Jan 2005 18:12:20 +0100 To: "PostgreSQL Perfomance" Subject: Re: Bitmap indexes References: <33c6269f0501280739344f6a18@mail.gmail.com> <2472.1106928826@sss.pgh.pa.us> Message-ID: Date: Fri, 28 Jan 2005 18:14:14 +0100 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <2472.1106928826@sss.pgh.pa.us> User-Agent: Opera M2/7.54 (Linux, build 751) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/585 X-Sequence-Number: 10275 > There's a great deal about this in the list archives (probably more in > pgsql-hackers than in -performance). Most of the current interest has > to do with building in-memory bitmaps on the fly, as a way of decoupling > index and heap scan processing. Which is not quite what you're talking > about but should be pretty effective for low-cardinality cases. In > particular it'd allow AND and OR combination of multiple indexes, which > we do poorly or not at all at the moment. Is this called a star join ? It would also allow to access the data pages in a more sequential order if the rows are not required to be retrieved in index order, which would potentially be a large speedup for index scans concerning more than the usual very small percentage of rows in a table : if several rows to be retrieved are on the same page, it would visit this page only once.