Simple select give wrong result when it uses the Bitmap Heap Scan path. <br /><br /><br /> postgres=# CREATE OR REPLACE FUNCTIONmy_exec_im_test_func(i integer) RETURNS integer AS $$ <br /> BEGIN <br /> RETURN i + 1;<br /> END;<br />$$ LANGUAGE plpgsql;<br />CREATE FUNCTION<br /><br />postgres=# setenable_seqscan=off;<br />SET<br />postgres=# set enable_indexscan=off;<br />SET<br />postgres=# select proname from pg_procwhere proname like 'my_pro1';<br /> proname <br />----------------------<br /> my_exec_im_test_proc<br/>(1 row)<br /><br />postgres=# explain select proname from pg_proc where proname like 'my_pro1';<br/> QUERY PLAN <br /> <br />--------------------------------------------------------------------------------<br />-------------<br /> Bitmap Heap Scanon pg_proc (cost=4.26..8.27 rows=1 width=64)<br /> Recheck Cond: (proname ~~ 'my_pro1'::text)<br /> -> BitmapIndex Scan on pg_proc_proname_args_nsp_index (cost=0.00..4.26 row<br />s=1 width=0)<br /> Index Cond: ((proname>= 'my'::name) AND (proname < 'mz'::name))<br />(4 rows)<br /><br /><br /><br clear="all" /><br />-- <br />RushabhLathia<br /><br /><a href="http://www.EnterpriseDB.com">www.EnterpriseDB.com</a>
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных