From: PFC <lists@boutiquenumerique.com>
To: PostgreSQL Perfomance <pgsql-performance@postgresql.org>
Subject: Re: Bitmap indexes
Date: Fri, 28 Jan 2005 18:14:14 +0100
Message-ID: <opslbot0keth1vuj@musicbox> (raw)
In-Reply-To: <2472.1106928826@sss.pgh.pa.us>
References: <33c6269f0501280739344f6a18@mail.gmail.com>
<2472.1106928826@sss.pgh.pa.us>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@boutiquenumerique.com
Subject: Re: Bitmap indexes
In-Reply-To: <opslbot0keth1vuj@musicbox>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox