Thread: BTP_CHAIN errors fixed?

Hi,
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
(just want to know before I put this into production :-))?

Thanks,
Mark

Mark Volpe <volpe.mark@epamail.epa.gov> 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

Tom Lane wrote:
> 
> Mark Volpe <volpe.mark@epamail.epa.gov> 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!