Skip to content

Commit bea2461

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 524712c commit bea2461

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
@@ -1909,8 +1909,11 @@ include_dir 'conf.d'
19091909
There is a separate server
19101910
process called the <firstterm>background writer</firstterm>, whose function
19111911
is to issue writes of <quote>dirty</quote> (new or modified) shared
1912-
buffers. It writes shared buffers so server processes handling
1913-
user queries seldom or never need to wait for a write to occur.
1912+
buffers. When the number of clean shared buffers appears to be
1913+
insufficient, the background writer writes some dirty buffers to the
1914+
file system and marks them as clean. This reduces the likelihood
1915+
that server processes handling user queries will be unable to find
1916+
clean buffers and have to write dirty buffers themselves.
19141917
However, the background writer does cause a net overall
19151918
increase in I/O load, because while a repeatedly-dirtied page might
19161919
otherwise be written only once per checkpoint interval, the

0 commit comments

Comments
 (0)