pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Comparing Parameters PRE- and POST- Upgrade - Any script?
Date: Thu, 6 Mar 2025 10:28:00 +0200
Message-ID: <37d3687a-5a1a-46ee-8b6c-0712b4069336@cloud.gatewaynet.com> (raw)
In-Reply-To: <CA+wokJ9N04u2xr5swC4KDufieb617-idM5AS6M9je2dT58wLfw@mail.gmail.com>
References: <CA+wokJ9N04u2xr5swC4KDufieb617-idM5AS6M9je2dT58wLfw@mail.gmail.com>


On 3/5/25 22:54, Edwin UY wrote:
> Hi,
>
> Does anyone know of a script that can be used to compare parameters 
> pre- and post- upgrade?
> Is it something that's worth the effort though? Or is it not something 
> to be worrying about?
> We only need to check pg_settings for this, is that correct?

Basically those the difference can be divided in the following categories :

a) parameters that are not supported any more in the new version

b) parameters that are introduced in the new version

c) parameters that have changed their name across the two versions and 
maybe the unit as well

So you have to isolate all non defaults from the old cluster and then 
read the docs and plan about all actions related to the GUC params in 
a), b)  and c) . Usually grep, ripgrep, awk, sort, uniq, and all the 
unix goodies along pg_settings are your friends to find differences.

Across more "distant" upgrades (I did pgsql10 -> pgsql16 recently) it 
becomes more painful. Across more close upgrades it is easier. If you 
dont know what to do with a new param, or dont have time to research, or 
benchmark, leave it to the default, and note this down to take into 
consideration in the next performance test. Some of them especially the 
new ones (e.g. JIT) sometimes might give tricky results so you may chose 
to be a little conservative and progress as you read and test things.






view thread (8+ messages)  latest in thread

Message-ID: <37d3687a-5a1a-46ee-8b6c-0712b4069336@cloud.gatewaynet.com>
Permalink:  ../37d3687a-5a1a-46ee-8b6c-0712b4069336@cloud.gatewaynet.com/
Also on:    postgresql.org/message-id/37d3687a-5a1a-46ee-8b6c-0712b4069336@cloud.gatewaynet.com

 · 

reply

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: a.mantzios@cloud.gatewaynet.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Comparing Parameters PRE- and POST- Upgrade - Any script?
  In-Reply-To: <37d3687a-5a1a-46ee-8b6c-0712b4069336@cloud.gatewaynet.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