Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit139c439

Browse files
committed
doc: update bgwriter description
This clarifies exactly what the bgwriter does, which should help withtuning.Reported-by: Chris WilsonDiscussion:https://postgr.es/m/160399562040.7809.7335281028960123489@wrigleys.postgresql.orgBackpatch-through: 9.5
1 parent3da1110 commit139c439

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

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp