Skip to content

Commit de56e96

Browse files
committed
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
1 parent 5491d78 commit de56e96

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

doc/src/sgml/config.sgml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1820,8 +1820,11 @@ include_dir 'conf.d'
18201820
There is a separate server
18211821
process called the <firstterm>background writer</>, whose function
18221822
is to issue writes of <quote>dirty</> (new or modified) shared
1823-
buffers. It writes shared buffers so server processes handling
1824-
user queries seldom or never need to wait for a write to occur.
1823+
buffers. When the number of clean shared buffers appears to be
1824+
insufficient, the background writer writes some dirty buffers to the
1825+
file system and marks them as clean. This reduces the likelihood
1826+
that server processes handling user queries will be unable to find
1827+
clean buffers and have to write dirty buffers themselves.
18251828
However, the background writer does cause a net overall
18261829
increase in I/O load, because while a repeatedly-dirtied page might
18271830
otherwise be written only once per checkpoint interval, the

0 commit comments

Comments
 (0)