X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C3558D84E6 for ; Tue, 30 Aug 2005 16:32:35 -0300 (ADT) 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 44660-03 for ; Tue, 30 Aug 2005 19:32:30 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7DCD4D7DD2 for ; Tue, 30 Aug 2005 16:32:28 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j7UJWQJT024116; Tue, 30 Aug 2005 15:32:26 -0400 (EDT) To: Scott Marlowe Cc: RAJU kumar , pgsql-admin@postgresql.org Subject: Re: Hash index In-reply-to: <1125428023.28179.94.camel@state.g2switchworks.com> References: <20050826105950.23187.qmail@webmail18.rediffmail.com> <1125428023.28179.94.camel@state.g2switchworks.com> Comments: In-reply-to Scott Marlowe message dated "Tue, 30 Aug 2005 13:53:43 -0500" Date: Tue, 30 Aug 2005 15:32:26 -0400 Message-ID: <24115.1125430346@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200508/394 X-Sequence-Number: 18713 Scott Marlowe 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