Re: bgwriter_lru_maxpages limits in PG 10 sample conf

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bgwriter_lru_maxpages limits in PG 10 sample conf
Date: 2019-02-20 19:35:27
Message-ID: CA+TgmoZm+nVC1nGneSA_T5DLryWkrSkzimwt1WqAihWS7h_4-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 20, 2019 at 5:53 AM Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> We increased bgwriter_lru_maxpages limit in 10 release [1]. Docs now are changed correctly but in REL_10_STABLE postgresql.conf.sample we still have comment "0-1000 max buffers written/round".
> Master (and REL_11_STABLE) was updated later in 611fe7d4793ba6516e839dc50b5319b990283f4f, but not REL_10. I think we need backpatch this line.

I'm a bit reluctant to whack postgresql.conf around in back-branches
because sometimes that makes funny things happen when somebody
upgrades, e.g. via RPM. I don't remember exactly what happens but I
think typically either the new file overwrites the existing file which
gets moved to something like postgresql.conf.rpmsave or the new file
is written into postgresql.conf.rpmnew instead of the original
location. I don't think it's worth making stuff like that happen for
the sake of a comment.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-20 19:41:06 Re: Proving IS NOT NULL inference for ScalarArrayOpExpr's
Previous Message Daniel Verite 2019-02-20 19:12:18 Re: Compressed TOAST Slicing