From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Fix pg_upgrade to detect non-upgradable anyarray usages. |
Date: | 2022-07-05 17:06:40 |
Message-ID: | E1o8m0V-001LYN-Gg@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix pg_upgrade to detect non-upgradable anyarray usages.
When we changed some built-in functions to use anycompatiblearray
instead of anyarray, we created a dump/restore hazard for user-defined
operators and aggregates relying on those functions: the user objects
have to be modified to change their signatures similarly. This causes
pg_upgrade to fail partway through if the source installation contains
such objects. We generally try to have pg_upgrade detect such hazards
and fail before it does anything exciting, so add logic to detect
this case too.
Back-patch to v14 where the change was made.
Justin Pryzby, reviewed by Andrey Borodin
Discussion: https://postgr.es/m/3383880.QJadu78ljV@vejsadalnx
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/09878cdd489ff7aca761998e7cb104f4fd98ae02
Modified Files
--------------
src/bin/pg_upgrade/check.c | 135 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 135 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-07-05 17:06:41 | pgsql: Fix pg_upgrade to detect non-upgradable anyarray usages. |
Previous Message | Tom Lane | 2022-07-05 15:12:43 | pgsql: Fix errors in copyfuncs/equalfuncs support for JSON node types. |