| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Increase the default value of cpu_index_tuple_cost from 0.001 to |
| Date: | 2006-06-05 03:03:42 |
| Message-ID: | 20060605030342.613209FA5C3@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-06-05 03:55:00 | pgsql: Have psql history save \e editor contents to history before query |
| Previous Message | Tom Lane | 2006-06-05 02:49:59 | pgsql: Add a GUC parameter seq_page_cost, and use that everywhere we |