Re: bgwriter_lru_maxpages range in postgresql.conf - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: bgwriter_lru_maxpages range in postgresql.conf
Date
Msg-id CAMkU=1yWOvL+YFYzGM9yXSoWjxr_5_Ny78pPzLKQCkfgB7H-JQ@mail.gmail.com
Whole thread Raw
In response to Re: bgwriter_lru_maxpages range in postgresql.conf  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: bgwriter_lru_maxpages range in postgresql.conf  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Nov 16, 2017 at 11:10 AM, Robert Haas <robertmhaas@gmail.com> wrote:
On Thu, Nov 16, 2017 at 1:26 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> (My earlier post has been stuck in infinite moderation due to the use of a
> common 6 letter abbreviation for configuration, so I will try again without
> it)
>
> With v10, commit 14ca9abfbe4643408a, the upper limit on
> bgwriter_lru_maxpages was changed from 1000 to INT_MAX / 2, but the
> postgresql.conf.sample was not updated.
>
> #bgwriter_lru_maxpages = 100        # 0-1000 max buffers written/round
>
> I don't see any precedence for including INT_MAX-type limits in the sample
> configuration file, so maybe something like this:?
>
> #bgwriter_lru_maxpages = 100        # max buffers written/round, 0 to turn
> off

wfm.  Patch?

I changed it to "0 disables" to be more consistent with other locations.

Cheers,

Jeff
Attachment

pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: [HACKERS] [PATCH] Generic type subscripting
Next
From: Michael Paquier
Date:
Subject: Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256