From 0f8fc35a5a9824d4f50edef49ce000f104ca5e74 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 25 Sep 2006 22:12:24 +0000 Subject: Increase default value of effective_cache_size to 128MB, per discussion. --- doc/src/sgml/config.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index a4e3eb020bb..b3223e3de43 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -1905,7 +1905,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows Sets the planner's assumption about the effective size of the - disk cache that is available to a single index scan. This is + disk cache that is available to a single query. This is factored into estimates of the cost of using an index; a higher value makes it more likely index scans will be used, a lower value makes it more likely sequential scans will be @@ -1913,13 +1913,13 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows PostgreSQL's shared buffers and the portion of the kernel's disk cache that will be used for PostgreSQL data files. Also, take - into account the expected number of concurrent queries using - different indexes, since they will have to share the available + into account the expected number of concurrent queries on different + tables, since they will have to share the available space. This parameter has no effect on the size of shared memory allocated by PostgreSQL, nor does it reserve kernel disk cache; it is used only for estimation purposes. The value is measured in disk pages, - which are normally 8192 bytes each. The default is 1000. + which are normally 8192 bytes each. The default is 16384 (128 MB). -- cgit v1.2.3