Log Message:
-----------
Increase the default value of cpu_index_tuple_cost from 0.001 to 0.005.
This shouldn't affect simple indexscans much, while for bitmap scans that
are touching a lot of index rows, this seems to bring the estimates more
in line with reality.  Per recent discussion.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        config.sgml (r1.60 -> r1.61)
        
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.60&r2=1.61)
    pgsql/src/backend/utils/misc:
        postgresql.conf.sample (r1.178 -> r1.179)
        
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.178&r2=1.179)
    pgsql/src/include/optimizer:
        cost.h (r1.74 -> r1.75)
        
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/cost.h.diff?r1=1.74&r2=1.75)

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to