Re: bug in index?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Martin, Sylvain R(dot) (LNG)" <Sylvain(dot)Martin(at)lexis-nexis(dot)com>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: bug in index?
Date: 2000-07-07 19:37:14
Message-ID: 11705.962998634@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I had your prior message on my "to look at" list; the behavior seems
pretty odd. Two questions:

1. Which version are you running, exactly?

2. Might 'peripherals & access' happen to be the largest (last in
sort order) keyword present in your table?

If #2 is true, then this might represent some sort of boundary-condition
misbehavior in the cost estimator. But I don't see anything like it
happening in current sources.

regards, tom lane

In response to

  • bug in index? at 2000-07-07 18:56:07 from Martin, Sylvain R. (LNG)

Browse pgsql-bugs by date

  From Date Subject
Next Message ryan 2000-07-07 21:30:03 "New" bug?? Serious - crashes backend.
Previous Message Bruce Momjian 2000-07-07 19:13:05 Re: ps_status.h on FreeBSD 4.0 problems and fix