From: Tom Lane <tgl@sss.pgh.pa.us>
To: Luke Lonergan <LLonergan@greenplum.com>
Cc: mark@mark.mielke.cc, "Bruce Momjian" <bruce@momjian.us>
Cc: Jie Zhang <jzhang@greenplum.com>
Cc: Hannu Krosing <hannu@skype.net>
Cc: Gavin Sherry <swm@linuxworld.com.au>
Cc: pgsql-hackers@postgresql.org
Subject: Re: On-disk bitmap index patch
Date: Tue, 25 Jul 2006 13:06:28 -0400
Message-ID: <17917.1153847188@sss.pgh.pa.us> (raw)
In-Reply-To: <3E37B936B592014B978C4415F90D662D01F73ACF@MI8NYCMAIL06.Mi8.com>
References: <3E37B936B592014B978C4415F90D662D01F73ACF@MI8NYCMAIL06.Mi8.com>
"Luke Lonergan" <LLonergan@greenplum.com> writes:
> I think we do know, have you reviewed the results in the briefing?
I find those results moderately unconvincing, primarily because they
are based on choosing the least efficient possible data representation
(viz char(n)), and thus the btree indexes suffer severe and quite
artificial bloat. A database schema chosen with even minimal attention
to PG-specific tuning would probably have btree indexes half the size.
That wouldn't completely eliminate the performance differential shown,
but it would bring it down into the ballpark where you have to question
whether it makes sense to support another index AM.
The reason I have such high sales resistance is that we've carried the
hash and rtree AMs for years, hoping that someone would do the work to
make them actually worth using, with little result. I don't want any
more second-class-citizen index AMs, and that's why I'm questioning
what the scope of applicability of bitmap indexes really is. They need
to be popular enough that people will be motivated to work on them,
or they shouldn't be in core.
regards, tom lane
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, LLonergan@greenplum.com, bruce@momjian.us, jzhang@greenplum.com, hannu@skype.net, swm@linuxworld.com.au
Subject: Re: On-disk bitmap index patch
In-Reply-To: <17917.1153847188@sss.pgh.pa.us>
* 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