postgres.git / summary / log / commit / refs

commit    de56e96ac83d2745566d36fd03617561ee026a2b
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Mon Nov 16 18:13:43 2020 +0000

    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


 doc/src/sgml/config.sgml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index f091b084956..b2dd54f5acb 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1820,8 +1820,11 @@ include_dir 'conf.d'
       There is a separate server
       process called the <firstterm>background writer</>, whose function
       is to issue writes of <quote>dirty</> (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


[parent: 5491d7829e7e]