From: Michael Paquier <michael@paquier.xyz>
To: chris+postgresql@qwirx.com
To: pgsql-docs@lists.postgresql.org
Subject: Re: bgwriter_lru_multiplier maximum value
Date: Mon, 1 Apr 2019 22:18:09 +0900
Message-ID: <20190401131809.GD16093@paquier.xyz> (raw)
In-Reply-To: <155411443331.724.3765587776420552242@wrigleys.postgresql.org>
References: <155411443331.724.3765587776420552242@wrigleys.postgresql.org>
On Mon, Apr 01, 2019 at 10:27:13AM +0000, PG Doc comments form wrote:
> The server has an undocumented maximum value of 10 for
> bgwriter_lru_multiplier, and will fail to start if it's set higher than
> this:
>
> LOG: 20 is outside the valid range for parameter "bgwriter_lru_multiplier"
> (0 .. 10)
> FATAL: configuration file "/.../pgdata/postgresql.conf" contains errors
I would suggest something like that:
inline patch 1: doc/src/sgml/config.sgml (+2/-1 lines) download inline-1.patch--- a/doc/src/sgml/config.sgml+++ b/doc/src/sgml/config.sgml@@ -2050,7 +2050,8 @@ include_dir 'conf.d'
Larger values provide some cushion against spikes in demand,
while smaller values intentionally leave writes to be done by
server processes.
- The default is 2.0.+ The default is 2.0. The value can range from <literal>2.0</literal>+ to <literal>10.0</literal>
This parameter can only be set in the <filename>postgresql.conf</filename>
file or on the server command line.
</para>
Any opinions from others?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, chris+postgresql@qwirx.com, pgsql-docs@lists.postgresql.org
Subject: Re: bgwriter_lru_multiplier maximum value
In-Reply-To: <20190401131809.GD16093@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox