Skip to content

Commit 7fc0c4c

Browse files
committed
GUC: adjust effective_cache_size docs and SQL description
Clarify that effective_cache_size is both kernel buffers and shared buffers. Reported-by: nat@makarevitch.org Discussion: https://postgr.es/m/153685164808.22334.15432535018443165207@wrigleys.postgresql.org Backpatch-through: 9.3
1 parent f499dab commit 7fc0c4c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

doc/src/sgml/config.sgml

+2-1
Original file line numberDiff line numberDiff line change
@@ -2902,7 +2902,8 @@ include 'filename'
29022902
used. When setting this parameter you should consider both
29032903
<productname>PostgreSQL</productname>'s shared buffers and the
29042904
portion of the kernel's disk cache that will be used for
2905-
<productname>PostgreSQL</productname> data files. Also, take
2905+
<productname>PostgreSQL</productname> data files, though some
2906+
data might exist in both places. Also, take
29062907
into account the expected number of concurrent queries on different
29072908
tables, since they will have to share the available
29082909
space. This parameter has no effect on the size of shared

src/backend/utils/misc/guc.c

+3-4
Original file line numberDiff line numberDiff line change
@@ -2406,10 +2406,9 @@ static struct config_int ConfigureNamesInt[] =
24062406

24072407
{
24082408
{"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
2409-
gettext_noop("Sets the planner's assumption about the size of the disk cache."),
2410-
gettext_noop("That is, the portion of the kernel's disk cache that "
2411-
"will be used for PostgreSQL data files. This is measured in disk "
2412-
"pages, which are normally 8 kB each."),
2409+
gettext_noop("Sets the planner's assumption about the size of the data cache."),
2410+
gettext_noop("That is, the size of the cache used for PostgreSQL data files. "
2411+
"This is measured in disk pages, which are normally 8 kB each."),
24132412
GUC_UNIT_BLOCKS,
24142413
},
24152414
&effective_cache_size,

0 commit comments

Comments
 (0)