From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Rushabh Lathia" <rushabh(dot)lathia(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, heikki(at)enterprisedb(dot)com, rushabh(dot)lathia(at)enterprisedb(dot)com |
Subject: | Re: Problem with Bitmap Heap Scan |
Date: | 2008-11-19 18:46:26 |
Message-ID: | 17828.1227120386@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Rushabh Lathia" <rushabh(dot)lathia(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2008-11-19 19:42:22 | Re: TODO list request: FK to unique expression indexes |
Previous Message | Tom Lane | 2008-11-19 18:34:58 | Re: New bug |