Return-Path: owner-postman
Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id OAA26398 for postgres-dist; Thu, 2 Dec 1993 14:18:13 -0800
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199312022218.OAA26398@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from chorizo.CS.Berkeley.EDU (chorizo.CS.Berkeley.EDU [128.32.149.118]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id OAA26389 for <postgres@nobozo.CS.Berkeley.EDU>; Thu, 2 Dec 1993 14:18:12 -0800
Received: from localhost (marcel@localhost) by chorizo.CS.Berkeley.EDU (8.6.4/8.1B) id OAA11075; Thu, 2 Dec 1993 14:18:06 -0800
Date: Thu, 2 Dec 1993 14:07:18 -0800 (PST)
From: Marcel Kornacker <marcel@chorizo.CS.Berkeley.EDU>
Subject: Re: problem with btree indexes
To: John Peter Lee <jlee@cs.uml.edu>
cc: postgres@postgres.Berkeley.EDU, JP Lee <jlee@cs.uml.edu>,
        Dave Pinkney <dpinkney@cs.uml.edu>, "John C. Sieg" <john@cs.uml.edu>
In-Reply-To: <199312021355.AA15916@cs.uml.edu>
Message-ID: <Pine.3.87.9312021418.A11056-0100000@chorizo.CS.Berkeley.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-To: postgres-dist@postgres.Berkeley.EDU
Resent-Date: Thu, 02 Dec 93 14:18:13 -0800
Resent-XMts: smtp

John:

Yes, there was a bug in the btree code that's fixed now. Version 
4.1 still contained that bug, the next release won't. The problem was in 
the insert routine, which made later searches in the btree overlook 
some values. The only workaround for you now is to remove the index; when 
you receive the next release you will have to rebuild this index and 
possible others which also have this "bug" in them. 

The 2M for the index is actually reasonable, since the btree has to store 
one key/tupleID-pair for each record in the indexed relation.

Marcel.