summaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorTom Lane2006-06-05 03:03:42 +0000
committerTom Lane2006-06-05 03:03:42 +0000
commite4de635a2ba10dcc6fdb972f87fb25953d8d3001 (patch)
treea6262df8a6f38a39ad222147749222f41d2210ad /src/backend
parenteed6c9ed7e243948e440ed1388591b7fa28f5827 (diff)
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.
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/utils/misc/postgresql.conf.sample2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index 0499223d110..ee5adaa2ff2 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -178,7 +178,7 @@
#seq_page_cost = 1.0 # measured on an arbitrary scale
#random_page_cost = 4.0 # same scale as above
#cpu_tuple_cost = 0.01 # same scale as above
-#cpu_index_tuple_cost = 0.001 # same scale as above
+#cpu_index_tuple_cost = 0.005 # same scale as above
#cpu_operator_cost = 0.0025 # same scale as above
#effective_cache_size = 1000 # typically 8KB each