Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Subject: Re: Comparing Parameters PRE- and POST- Upgrade - Any script?
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CA+wokJ_eK9RTaRYXfVaCSfzfbc1Xn2TxTXfjOOBdWv9DP=yG0Q@mail.gmail.com>
Date: Wed, 5 Mar 2025 14:24:11 -0700
Cc: Ron Johnson <ronljohnsonjr@gmail.com>,
 Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E4F62CA-BFEA-4F54-B1CB-F47D23CA32E1@elevated-dev.com>
References: 
 <CA+wokJ9N04u2xr5swC4KDufieb617-idM5AS6M9je2dT58wLfw@mail.gmail.com>
 <CANzqJaCHY6GmKDmv_x-2q9LgNhRW=CG8oQ=Fx7ciE_QrKQ5o5w@mail.gmail.com>
 <CA+wokJ_eK9RTaRYXfVaCSfzfbc1Xn2TxTXfjOOBdWv9DP=yG0Q@mail.gmail.com>
To: Edwin UY <edwin.uy@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/5E4F62CA-BFEA-4F54-B1CB-F47D23CA32E1%40elevated-dev.com>
Precedence: bulk

> On Mar 5, 2025, at 2:18=E2=80=AFPM, Edwin UY <edwin.uy@gmail.com> =
wrote:
>=20
> Thanks, I thought pg_upgrade will somehow insert/update it with new =
parameters of sorts.

No. So you wind up with new parameters just getting defaults, and not =
specified or documented in the file.

Couple of ways around this:

- Put your parameters in a separate file that's included into =
postgresql.conf.
- Generate a new db, diff its config against the old one to see what's =
new that you might want to change, and use it with the inclusion of your =
settings.=