Commit 2e92b587 authored by Heikki Linnakangas's avatar Heikki Linnakangas

Mention in the docs that bgwriter now sleeps longer when it has no work to do.

parent 3946c281
...@@ -1322,12 +1322,14 @@ SET ENABLE_SEQSCAN TO OFF; ...@@ -1322,12 +1322,14 @@ SET ENABLE_SEQSCAN TO OFF;
background writer. In each round the writer issues writes background writer. In each round the writer issues writes
for some number of dirty buffers (controllable by the for some number of dirty buffers (controllable by the
following parameters). It then sleeps for <varname>bgwriter_delay</> following parameters). It then sleeps for <varname>bgwriter_delay</>
milliseconds, and repeats. The default value is 200 milliseconds milliseconds, and repeats. When there are no dirty buffers in the
(<literal>200ms</>). Note that on many systems, the effective buffer pool, though, it goes into a longer sleep regardless of
resolution of sleep delays is 10 milliseconds; setting <varname>bgwriter_delay</>. The default value is 200
<varname>bgwriter_delay</> to a value that is not a multiple of milliseconds (<literal>200ms</>). Note that on many systems, the
10 might have the same results as setting it to the next higher effective resolution of sleep delays is 10 milliseconds; setting
multiple of 10. This parameter can only be set in the <varname>bgwriter_delay</> to a value that is not a multiple of 10
might have the same results as setting it to the next higher multiple
of 10. This parameter can only be set in the
<filename>postgresql.conf</> file or on the server command line. <filename>postgresql.conf</> file or on the server command line.
</para> </para>
</listitem> </listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment