Re: [18] Policy on IMMUTABLE functions and Unicode updates

Jeremy Schneider <schneider@ardentperf.com>

From: Jeremy Schneider <schneider@ardentperf.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Daniel Verite <daniel@manitou-mail.org>, Jeff Davis <pgsql@j-davis.com>, Joe Conway <mail@joeconway.com>, LaurenzAlbe <laurenz.albe@cybertec.at>, Noah Misch <noah@leadboat.com>, Peter Eisentraut <peter@eisentraut.org>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2024-07-16T20:41:08Z
Lists: pgsql-hackers
On Tue, Jul 16, 2024 at 3:28 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:

>
> I'd teach pg_upgrade to inspect the post-upgraded catalog of in-use
> dependencies and report on any of these it finds and remind the DBA that
> this latent issue may exist in their system.
>

Would this help? Collation-related dependency changes are a different thing
from major version DB upgrades

Tom’s point about how the levels are directly tied to concrete differences
in behavior (planner/executor) makes a lot of sense to me

-Jeremy