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 AAE1C3A60FB for ; Fri, 28 Jan 2005 15:40:01 +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 63711-06 for ; Fri, 28 Jan 2005 15:39:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by svr1.postgresql.org (Postfix) with ESMTP id 140953A634C for ; Fri, 28 Jan 2005 15:39:51 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 71so460012wra for ; Fri, 28 Jan 2005 07:39:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=rviPLqth8Hdf86DCpPJ12212TznDxzqsoytxuM1+qvo33Jut1Mw+DSDtw15JEKGNwSHvWVTvEQxwHkwaJ++FaOBBNZxB/klbvVWBsmz438kMCfzcpjW+IlOlb5FJWPUUiszz7LwHQd+4HiLzgv2ip3TnAcPhDXlKnxAZK11nyCY= Received: by 10.54.38.67 with SMTP id l67mr151002wrl; Fri, 28 Jan 2005 07:39:52 -0800 (PST) Received: by 10.54.18.72 with HTTP; Fri, 28 Jan 2005 07:39:52 -0800 (PST) Message-ID: <33c6269f0501280739344f6a18@mail.gmail.com> Date: Fri, 28 Jan 2005 10:39:52 -0500 From: Alex Turner Reply-To: alex@neteconomist.com To: PostgreSQL Perfomance Subject: Bitmap indexes Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.038 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200501/575 X-Sequence-Number: 10265 I was wondering about index types. Oracle has an index type called a 'bitmap' index. They describe this as an index for low cardinality fields, where only the cardinal values are indexed in a b-tree, and then it uses a bitmap below that to describe rows. They say that this type of index is very fast when combined with queries that used the indexed row in 'AND' clauses in a sql statement as the index can 'mask' the results very fast. I have not been able to benchmark the actual effectiveness of this kind of index, but I was wondering if anyone has had experience with this an believes it might be a useful feature for postgres? Yes I have a vested interest in this because alot of my searches are masked against low cardinality fields 'Y' or 'N' type things where this could potentialy benefit me... Alex Turner NetEconomist