Re: bgwriter_lru_maxpages limits in PG 10 sample conf

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: 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-02-22 00:58:51
Message-ID: 20190222005851.ytr3ricmenxgmnk7@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 20, 2019 at 11:54:25PM +0300, Sergei Kornilov wrote:
> Hello
>
> > 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.
>
> If i remember correctly both deb and rpm packages will ask user about config difference.
> But good point, comment change is too small difference. I am a bit late, good time for such change was before last minor release (we add data_sync_retry and config was changed anyway).

The other issue is that you will change share/postgresql.conf.sample,
but not $PGDATA/postgresql.conf until initdb is run, meaning if someone
diffs the two files, they will see differences that they did not make.
Making defaults more accurate is not worth that confusion.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2019-02-22 01:03:19 RE: Timeout parameters
Previous Message Iwata, Aya 2019-02-22 00:52:09 RE: libpq debug log