aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeProjectSet.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-07-05 13:06:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-07-05 13:06:31 -0400
commitc069f427855a486a4d32d84e2bf4c932df00d7d5 (patch)
tree4571900ec7515098f2611123db54970d5a29e7c8 /src/backend/executor/nodeProjectSet.c
parent90d6c65a2c2358bd80103afc0686c90c70d5417b (diff)
downloadpostgresql-c069f427855a486a4d32d84e2bf4c932df00d7d5.tar.gz
postgresql-c069f427855a486a4d32d84e2bf4c932df00d7d5.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/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions