From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(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 19:10:30 |
Message-ID: | CA+TgmobFsKKO9L0YJZ4eNsdv2Oxf4M4YuN85UZxs6J2Rdt2yPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-11-16 19:18:02 | Re: Typo in comment |
Previous Message | Peter Eisentraut | 2017-11-16 18:36:09 | Re: Transaction control in procedures |