Re: Problem with Bitmap Heap Scan - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Problem with Bitmap Heap Scan
Date
Msg-id 17828.1227120386@sss.pgh.pa.us
Whole thread Raw
In response to Problem with Bitmap Heap Scan  ("Rushabh Lathia" <rushabh.lathia@gmail.com>)
Responses Re: Problem with Bitmap Heap Scan  (rushabh <rushabh.lathia@enterprisedb.com>)
Re: Problem with Bitmap Heap Scan  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
"Rushabh Lathia" <rushabh.lathia@gmail.com> writes:
> Simple select give wrong result when it uses the Bitmap Heap Scan path.

It's generally appropriate to mention which PG version you're working
with when you report a bug.

> postgres=# explain select proname from pg_proc where proname like 'my_pro1';
>                                          QUERY
> PLAN

> --------------------------------------------------------------------------------
> -------------
>  Bitmap Heap Scan on pg_proc  (cost=4.26..8.27 rows=1 width=64)
>    Recheck Cond: (proname ~~ 'my_pro1'::text)
>    ->  Bitmap Index Scan on pg_proc_proname_args_nsp_index  (cost=0.00..4.26
> row
> s=1 width=0)
>          Index Cond: ((proname >= 'my'::name) AND (proname < 'mz'::name))
> (4 rows)

Hmm, the ~~ condition should get treated as a "filter" not a "recheck".
I suppose I broke this somewhere ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: New bug
Next
From: "David E. Wheeler"
Date:
Subject: Re: TODO list request: FK to unique expression indexes