From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Edwin UY <edwin.uy@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Comparing Parameters PRE- and POST- Upgrade - Any script?
Date: Wed, 5 Mar 2025 14:24:11 -0700
Message-ID: <5E4F62CA-BFEA-4F54-B1CB-F47D23CA32E1@elevated-dev.com> (raw)
In-Reply-To: <CA+wokJ_eK9RTaRYXfVaCSfzfbc1Xn2TxTXfjOOBdWv9DP=yG0Q@mail.gmail.com>
References: <CA+wokJ9N04u2xr5swC4KDufieb617-idM5AS6M9je2dT58wLfw@mail.gmail.com>
<CANzqJaCHY6GmKDmv_x-2q9LgNhRW=CG8oQ=Fx7ciE_QrKQ5o5w@mail.gmail.com>
<CA+wokJ_eK9RTaRYXfVaCSfzfbc1Xn2TxTXfjOOBdWv9DP=yG0Q@mail.gmail.com>
> On Mar 5, 2025, at 2:18 PM, Edwin UY <edwin.uy@gmail.com> wrote:
>
> 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.
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-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, edwin.uy@gmail.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Comparing Parameters PRE- and POST- Upgrade - Any script?
In-Reply-To: <5E4F62CA-BFEA-4F54-B1CB-F47D23CA32E1@elevated-dev.com>
* 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