From: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, LaurenzAlbe <laurenz(dot)albe(at)cybertec(dot)at>, Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
Date: | 2024-07-16 20:41:08 |
Message-ID: | CA+fnDAY0-H03nec_OC6MgCdM0rV7+QGRGJ9YZ8i6y0FNXO04dg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 16, 2024 at 3:28 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2024-07-16 20:47:08 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
Previous Message | David G. Johnston | 2024-07-16 20:27:28 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |