pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: RAJU kumar <raju_19db@rediffmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Hash index
Date: Tue, 30 Aug 2005 13:53:43 -0500
Message-ID: <1125428023.28179.94.camel@state.g2switchworks.com> (raw)
In-Reply-To: <20050826105950.23187.qmail@webmail18.rediffmail.com>
References: <20050826105950.23187.qmail@webmail18.rediffmail.com>

On Fri, 2005-08-26 at 05:59, RAJU kumar wrote:
>   
>   
> i want to find out the difference between the btree index and hash
> index and how exactly the hash index work.

How do hash indexes work in postgresql?  Poorly.  badumpbump.  Thanks,
I'll be here all week (bad western humor, sorry.)

Seriously, there are issues that pop up here every so often that stump
people until we find out that they're using hash indexes and every goes
"Ohhhhh!  That's why X isn't working for you."

Currently, only btree indexes are handled properly in case of a server
crash (other indexes may get corrupted silently) and they are generally
as fast as or faster than hashes.

The basic concept in postgresql is the same as elsewhere, but they've
never been fleshed out properly, especially compared to btree, which
have had lots of testing and fixing and performance tuning and such.

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.



view thread (10+ messages)  latest in thread

Message-ID: <1125428023.28179.94.camel@state.g2switchworks.com>
Permalink:  ../1125428023.28179.94.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1125428023.28179.94.camel@state.g2switchworks.com

 · 

reply

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: smarlowe@g2switchworks.com, raju_19db@rediffmail.com
  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>

* 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