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

Commit62b50ad

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 parent8ad06bc commit62b50ad

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

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp