Re: Problem with Bitmap Heap Scan
От | Tom Lane |
---|---|
Тема | Re: Problem with Bitmap Heap Scan |
Дата | |
Msg-id | 17828.1227120386@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Problem with Bitmap Heap Scan ("Rushabh Lathia" <rushabh.lathia@gmail.com>) |
Ответы |
Re: Problem with Bitmap Heap Scan
Re: Problem with Bitmap Heap Scan |
Список | 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 по дате отправления: