Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0RN0Vq99091 for ; Sat, 27 Jan 2001 18:00:31 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0RN0R924209; Sat, 27 Jan 2001 18:00:28 -0500 (EST) To: Mark Volpe cc: pgsql-sql@postgresql.org Subject: Re: BTP_CHAIN errors fixed? In-reply-to: <3A734EF3.FF998713@epamail.epa.gov> References: <3A734EF3.FF998713@epamail.epa.gov> Comments: In-reply-to Mark Volpe message dated "Sat, 27 Jan 2001 17:42:59 -0500" Date: Sat, 27 Jan 2001 18:00:27 -0500 Message-ID: <24206.980636427@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/420 X-Sequence-Number: 1096 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