Re: BUG #2075: Strange choice of bitmap-index-scan

From: Arjen van der Meijden <acmmailing(at)tweakers(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2075: Strange choice of bitmap-index-scan
Date: 2005-11-29 16:43:17
Message-ID: 438C8525.2070501@tweakers.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

The "zichtbaar" as false is indeed a very rare case and appearantly
isn't occuring right now. There are indeed 46631 rows in total, and all
46631 have the "zichtbaar" as true. Which reminds me to adjust the index
anyway ;-)

It appears to be happening if the fraction of zichtbaar's is small
enough. With 1 and 8 as false, it happens, with 27 as false its not
happening.

Best regards,

Arjen

Tom Lane wrote:
> "Arjen" <acmmailing(at)tweakers(dot)net> writes:
>> -> BitmapAnd (cost=5.62..5.62 rows=1 width=0)
>> -> Bitmap Index Scan on pwprodukten_cat2_popuindex
>> (cost=0.00..2.50 rows=144 width=0)
>> Index Cond: (cat2 = 51)
>> -> Bitmap Index Scan on pwprodukten_cat2_zichtbaar
>> (cost=0.00..2.86 rows=144 width=0)
>> Index Cond: ((cat2 = 51) AND (zichtbaar = true))
>
> Hmmm ... I can reproduce that if *all* the rows in the table have
> zichtbaar = true (or at least the ANALYZE stats say so) ... is that
> the case in your data?
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-11-29 18:33:32 Re: postgres 8.1 crashing
Previous Message Kari Lavikka 2005-11-29 16:42:14 postgres 8.1 crashing