From: Daniel Gustafsson <daniel@yesql.se>
To: h@husseinnasser.com, pgsql-docs <pgsql-docs@lists.postgresql.org>
Subject: Re: bgwriter_delay
Date: Sun, 11 Feb 2024 23:19:20 +0100
Message-ID: <BAD3481D-D9DA-419A-98F6-9A2BEFCDC5CA@yesql.se> (raw)
In-Reply-To: <170752368082.3279718.1960370483154611839@wrigleys.postgresql.org>
References: <170752368082.3279718.1960370483154611839@wrigleys.postgresql.org>
> On 10 Feb 2024, at 01:08, PG Doc comments form <noreply@postgresql.org> wrote:
> Would be nice to add the limits to the doc, according to my pg15 instance I
> can't set bgwriter_delay more than 10000 ms. (I set it to 60 s and got a
> FATAL upon startup)
We do print the valid range for other bgwriter GUCs so it doesn't seem like an
unreasonable idea. It might not help too many, but not printing it at all
clearly doesn't really help anyone.
--
Daniel Gustafsson
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: daniel@yesql.se, pgsql-docs@lists.postgresql.org
Subject: Re: bgwriter_delay
In-Reply-To: <BAD3481D-D9DA-419A-98F6-9A2BEFCDC5CA@yesql.se>
* 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