Re: bgwriter_lru_maxpages limits in PG 10 sample conf - Mailing list pgsql-hackers

From Robert Haas
Subject Re: bgwriter_lru_maxpages limits in PG 10 sample conf
Date
Msg-id CA+TgmoZm+nVC1nGneSA_T5DLryWkrSkzimwt1WqAihWS7h_4-Q@mail.gmail.com
Whole thread Raw
In response to bgwriter_lru_maxpages limits in PG 10 sample conf  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: bgwriter_lru_maxpages limits in PG 10 sample conf  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
On Wed, Feb 20, 2019 at 5:53 AM Sergei Kornilov <sk@zsrv.org> wrote:
> We increased bgwriter_lru_maxpages limit in 10 release [1]. Docs now are changed correctly but in REL_10_STABLE
postgresql.conf.samplewe 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
needbackpatch 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


pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: Compressed TOAST Slicing
Next
From: Tom Lane
Date:
Subject: Re: Proving IS NOT NULL inference for ScalarArrayOpExpr's