Re: bgwriter_lru_maxpages range in postgresql.conf

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bgwriter_lru_maxpages range in postgresql.conf
Date: 2017-11-16 21:40:50
Message-ID: CAMkU=1yWOvL+YFYzGM9yXSoWjxr_5_Ny78pPzLKQCkfgB7H-JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 16, 2017 at 11:10 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, Nov 16, 2017 at 1:26 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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 Content-Type Size
lru_doc.patch application/octet-stream 900 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-11-16 21:50:34 Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256
Previous Message Dmitry Dolgov 2017-11-16 21:37:40 Re: [HACKERS] [PATCH] Generic type subscripting