Re: [18] Policy on IMMUTABLE functions and Unicode updates - Mailing list pgsql-hackers

From Jeremy Schneider
Subject Re: [18] Policy on IMMUTABLE functions and Unicode updates
Date
Msg-id CA+fnDAY0-H03nec_OC6MgCdM0rV7+QGRGJ9YZ8i6y0FNXO04dg@mail.gmail.com
Whole thread Raw
In response to Re: [18] Policy on IMMUTABLE functions and Unicode updates  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [18] Policy on IMMUTABLE functions and Unicode updates
Next
From: Jeff Davis
Date:
Subject: Re: [18] Policy on IMMUTABLE functions and Unicode updates