diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-07-05 13:06:31 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-07-05 13:06:31 -0400 |
| commit | 175e60a5e35e213f42ed69eeb5ab992a49ae41f4 (patch) | |
| tree | eef4900f258080c6c8767019c735c768fc6e531a /src/backend/utils/adt/tsquery_gist.c | |
| parent | 7c1f426123845c8be6a3a2791dbc0ebc87a92c40 (diff) | |
| download | postgresql-175e60a5e35e213f42ed69eeb5ab992a49ae41f4.tar.gz postgresql-175e60a5e35e213f42ed69eeb5ab992a49ae41f4.zip | |
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
Diffstat (limited to 'src/backend/utils/adt/tsquery_gist.c')
0 files changed, 0 insertions, 0 deletions