Re: Problem with Bitmap Heap Scan

Tom Lane wrote: <blockquote cite="mid:17828.1227120386@sss.pgh.pa.us" type="cite"><pre wrap="">"Rushabh Lathia" <a
class="moz-txt-link-rfc2396E"href="mailto:rushabh.lathia@gmail.com"><rushabh.lathia@gmail.com></a> writes:
</pre><blockquotetype="cite"><pre wrap="">Simple select give wrong result when it uses the Bitmap Heap Scan path.
</pre></blockquote><prewrap="">
 
It's generally appropriate to mention which PG version you're working
with when you report a bug.<tt></tt> </pre></blockquote><tt>I was on 8.4 CVS Head, Next time will sure take care of
this.</tt><br /><blockquote cite="mid:17828.1227120386@sss.pgh.pa.us" type="cite"><pre wrap=""> </pre><blockquote
type="cite"><prewrap="">postgres=# explain select proname from pg_proc where proname like 'my_pro1';
                   QUERY
 
PLAN   </pre></blockquote><pre wrap=""> </pre><blockquote type="cite"><pre
wrap="">--------------------------------------------------------------------------------
-------------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)   </pre></blockquote><pre wrap="">
Hmm, the ~~ condition should get treated as a "filter" not a "recheck".
I suppose I broke this somewhere ... </pre></blockquote><tt>Oh ok. </tt><br /><blockquote
cite="mid:17828.1227120386@sss.pgh.pa.us"type="cite"><pre wrap="">        regards, tom lane </pre></blockquote><br />