aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-11-16 13:13:43 -0500
committerBruce Momjian <bruce@momjian.us>2020-11-16 13:13:43 -0500
commit62b50ad698f8a789f92177ad72639f99d94d7d78 (patch)
tree57921fb6c14031f85af323dcf2ad974de7a46641
parent8ad06bcbe136360296a804da7d7631a78fd15e70 (diff)
downloadpostgresql-62b50ad698f8a789f92177ad72639f99d94d7d78.tar.gz
postgresql-62b50ad698f8a789f92177ad72639f99d94d7d78.zip
doc: update bgwriter description
This clarifies exactly what the bgwriter does, which should help with tuning. Reported-by: Chris Wilson Discussion: https://postgr.es/m/160399562040.7809.7335281028960123489@wrigleys.postgresql.org Backpatch-through: 9.5
-rw-r--r--doc/src/sgml/config.sgml7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index f043433e318..a632cf98ba0 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2146,8 +2146,11 @@ include_dir 'conf.d'
There is a separate server
process called the <firstterm>background writer</firstterm>, whose function
is to issue writes of <quote>dirty</quote> (new or modified) shared
- buffers. It writes shared buffers so server processes handling
- user queries seldom or never need to wait for a write to occur.
+ buffers. When the number of clean shared buffers appears to be
+ insufficient, the background writer writes some dirty buffers to the
+ file system and marks them as clean. This reduces the likelihood
+ that server processes handling user queries will be unable to find
+ clean buffers and have to write dirty buffers themselves.
However, the background writer does cause a net overall
increase in I/O load, because while a repeatedly-dirtied page might
otherwise be written only once per checkpoint interval, the