Date: Mon, 31 Aug 2020 17:36:40 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: ALTER SYSTEM between upgrades
Message-ID: <20200831213640.GO13613@momjian.us>
References: <20200825185950.GD26852@momjian.us>
 <2B2E657A-8F23-47D2-B56B-395633DE3AD2@yesql.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2B2E657A-8F23-47D2-B56B-395633DE3AD2@yesql.se>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Wed, Aug 26, 2020 at 12:22:25AM +0200, Daniel Gustafsson wrote:
> >> One can argue whether those bulletpoints are sufficient for stressing the
> >> importance, but it's at least mentioned.  There is however no mention of
> >> postgresql.auto.conf which clearly isn't helping anyone, so we should fix that.
> >> 
> >> Taking that a step further, maybe we should mention additional config files
> >> which could be included via include directives?  There are tools out there who
> >> avoid changing the users postgresql.conf by injecting an include directive
> >> instead; they might've placed the included file alongside postgresql.conf.
> > 
> > I have developed the attached pg_upgrade doc patch to address this.
> 
> LGTM, thanks!

Patch applied,

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee