From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bgwriter_lru_maxpages limits in PG 10 sample conf |
Date: | 2019-03-05 03:24:14 |
Message-ID: | 20190305032414.GA20508@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-Mar-04, Bruce Momjian wrote:
> On Thu, Feb 28, 2019 at 10:28:44AM +0300, Sergei Kornilov wrote:
> > Hello
> >
> > postgresql.conf.sample was changed recently in REL_10_STABLE (commit ab1d9f066aee4f9b81abde6136771debe0191ae8)
> > So config will be changed in next minor release anyway. We have another reason to not fix bgwriter_lru_maxpages comment?
>
> Frankly, I was surprised postgresql.conf.sample was changed in a back
> branch since it will cause people who diff $PGDATA/postgresql.conf with
> share/postgresql.conf.sample to see differences they didn't make.
I think the set of people that execute diffs of their production conf
file against the sample file to be pretty small -- maybe even empty. If
you're really interested in knowing the changes you've done, you're more
likely to use a version control system on the file anyway.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-03-05 03:25:39 | Re: libpq debug log |
Previous Message | Michael Paquier | 2019-03-05 03:12:06 | Re: Online verification of checksums |