From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hannu Krosing <hannu@skype.net>
Cc: Luke Lonergan <LLonergan@greenplum.com>
Cc: mark@mark.mielke.cc, Bruce Momjian <bruce@momjian.us>
Cc: Jie Zhang <jzhang@greenplum.com>
Cc: Gavin Sherry <swm@linuxworld.com.au>
Cc: pgsql-hackers@postgresql.org
Subject: Re: On-disk bitmap index patch
Date: Tue, 25 Jul 2006 16:31:53 -0400
Message-ID: <24222.1153859513@sss.pgh.pa.us> (raw)
In-Reply-To: <1153852574.2924.15.camel@localhost.localdomain>
References: <3E37B936B592014B978C4415F90D662D01F73ACF@MI8NYCMAIL06.Mi8.com>
<17917.1153847188@sss.pgh.pa.us>
<1153852574.2924.15.camel@localhost.localdomain>
Hannu Krosing <hannu@skype.net> writes:
> Ühel kenal päeval, T, 2006-07-25 kell 13:06, kirjutas Tom Lane:
>> 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.
> What would be the use-case for hash indexes ? And what should be done to
> make them faster than btree ?
If we knew, we'd do it ;-) But no one's put enough effort into it
to find out.
> and was'nt the rtree index recently deprecated in favour of GIST
> implementation of the same ?
Yeah, we finally gave up on rtree entirely. I don't want to see any
other index AMs languishing in the closet like that. If bitmap can
hold its own to the extent that people are interested in working on
it/improving it, then great, but I'm worried that it's not going to
have a wide enough use-case to attract maintainers.
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, hannu@skype.net, LLonergan@greenplum.com, bruce@momjian.us, jzhang@greenplum.com, swm@linuxworld.com.au
Subject: Re: On-disk bitmap index patch
In-Reply-To: <24222.1153859513@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