Received: from nts1.rtp.epa.gov (nts1.rtp.epa.gov [134.67.208.208]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0RNBGq99980 for ; Sat, 27 Jan 2001 18:11:16 -0500 (EST) (envelope-from volpe.mark@epamail.epa.gov) Received: from epamail.epa.gov (scanmeifyoudare.rtp.epa.gov [134.67.139.14]) by nts1.rtp.epa.gov (8.9.3/8.9.3) with ESMTP id SAA31213; Sat, 27 Jan 2001 18:15:54 -0500 (EST) Message-ID: <3A73558F.4801779@epamail.epa.gov> Date: Sat, 27 Jan 2001 18:11:11 -0500 From: Mark Volpe X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgresql.org Subject: Re: BTP_CHAIN errors fixed? References: <3A734EF3.FF998713@epamail.epa.gov> <24206.980636427@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/421 X-Sequence-Number: 1097 Tom Lane wrote: > > Mark Volpe writes: > > I have been using PostgreSQL-7.0.0 and have had the problem that, when > > searching a btree index that contains large numbers of duplicate keys, > > Postgres crashes with a BTP_CHAIN error. Now that I have installed 7.1beta3 > > the problem has seemingly been fixed. Was this problem actually fixed > > somewhere between 7.0.0 and 7.1beta3, or am I just getting lucky right now > > Well, it was worked on ;-) ... that whole chunk of code was rewritten. > Whether it has new bugs remains to be seen, but the old bugs are gone... > > regards, tom lane Thanks for the quick response. The new code will get plenty of testing from me!