From: Daniel Gustafsson <daniel@yesql.se>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: ALTER SYSTEM between upgrades
Date: Tue, 14 Jul 2020 12:52:23 +0200
Message-ID: <08AD4526-75AB-457B-B2DD-099663F28040@yesql.se> (raw)
In-Reply-To: <20200713235849.GA32422@momjian.us>
References: <CAA4eK1K-Uc1UFP5PKZEZYGG3cnnQTksXGBgnU4BBUTVx+Y43Fw@mail.gmail.com>
<20200707201821.GA24503@alvherre.pgsql>
<20200713235849.GA32422@momjian.us>
> On 14 Jul 2020, at 01:58, Bruce Momjian <bruce@momjian.us> wrote:
> I am creating a new thread to discuss the question raised by Alvaro of
> how many ALTER SYSTEM settings are lost during major upgrades. Do we
> properly document that users should migrate their postgresql.conf _and_
> postgresql.auto.conf files during major upgrades? I personally never
> thought of this until now.
Transferring postgresql.conf is discussed to some degree in the documentation
for pg_upgrade:
11. Restore pg_hba.conf
If you modified pg_hba.conf, restore its original settings. It might
also be necessary to adjust other configuration files in the new
cluster to match the old cluster, e.g. postgresql.conf.
.. as well as upgrading via pg_dumpall:
4. Restore your previous pg_hba.conf and any postgresql.conf
modifications.
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.
cheers ./daniel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: daniel@yesql.se, bruce@momjian.us, alvherre@2ndquadrant.com, pgsql-docs@postgresql.org
Subject: Re: ALTER SYSTEM between upgrades
In-Reply-To: <08AD4526-75AB-457B-B2DD-099663F28040@yesql.se>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox