Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id PAA19812 for postgres-redist; Tue, 5 Mar 1996 15:46:32 -0800
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199603052346.PAA19812@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.37.53]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with ESMTP id PAA23156 for <postgres@postgres.Berkeley.EDU>; Tue, 5 Mar 1996 15:46:31 -0800
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id PAA01847; Tue, 5 Mar 1996 15:46:19 -0800
Message-Id: <199603052346.PAA01847@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
From: aoki@cs.berkeley.edu (Paul M. Aoki)
To: "V.Grabner" <zen@bononunu.gams.co.at>
Cc: avi@baan.nl, postgres@postgres.Berkeley.EDU
Subject: Re: hash indices
Reply-To: aoki@cs.berkeley.edu (Paul M. Aoki)
In-reply-to: Your message of Tue, 05 Mar 1996 22:06:36 +0100 
	     <199603052106.WAA09702@zen.gams.co.at> 
Date: Tue, 05 Mar 96 15:46:19 -0800
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Tue, 05 Mar 96 15:46:31 -0800
Resent-XMts: smtp

"V.Grabner" <zen@bononunu.gams.co.at> writes:
> We had the same problem when using hash indices. Hash indices
> alsways crashed the database when creating an index or inserting 
> > 50 rows into the table.
> 
> Do not use them, use btree indices instead.
> 
> I tried to trace the problem but I did not find it. I found
> out it always happend during the split of an hash page but I
> never found out why. Without documentation I was lost.

the hash index split code is really, really broken in 4.2.  it doesn't
surface until you hit some fill factor (i.e., get a bunch of page
collisions), but after that the hash index is corrupt.  i think the
fixes (bug fixes, taking out the bogus "high concurrency" locking,
rewriting the split code) made it into some release of pg95 or
another..
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/
