From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: RAJU kumar <raju_19db@rediffmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Hash index
Date: Tue, 30 Aug 2005 15:32:26 -0400
Message-ID: <24115.1125430346@sss.pgh.pa.us> (raw)
In-Reply-To: <1125428023.28179.94.camel@state.g2switchworks.com>
References: <20050826105950.23187.qmail@webmail18.rediffmail.com>
<1125428023.28179.94.camel@state.g2switchworks.com>
Scott Marlowe <smarlowe@g2switchworks.com> writes:
> Personally, I think that when one creates a non-btree index, one should
> get a warning saying that non-btree indexes are not necessarily
> transactionally safe in the event of a crash.
As of 8.1, GIST indexes are WAL-logged, so that would be inappropriate
anyway.
What I foresee happening (soon, 8.2 maybe) is that rtree will go away
completely; there isn't anything it can do that GIST can't do as well or
better, so there's no point in expending maintenance resources on it.
We're really only leaving it there for 8.1 because there's so much new,
as-yet-poorly-tested code involved in the GIST replacement opclasses.
That leaves hash. I'm hoping someone will step up and do WAL logging
for hash in the near future. Unlike rtree, I'm not expecting that we
might get rid of hash indexes. Even if the performance problems never
get fixed, we use hash index opclasses to manage datatype-specific
hashing for hash joins, hash aggregation, etc, so if we removed hash
indexes we'd need to find some other representation for all that.
Anyway, that's my two cents on the development roadmap for indexes.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, raju_19db@rediffmail.com
Subject: Re: Hash index
In-Reply-To: <24115.1125430346@sss.pgh.pa.us>
References: <20050826105950.23187.qmail@webmail18.rediffmail.com> <1125428023.28179.94.camel@state.g2switchworks.com> <24115.1125430346@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