diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-01-17 16:00:39 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-01-17 16:01:01 -0500 |
commit | 1136d81bfa7f902a14fd426a97ecd99381d72953 (patch) | |
tree | 2f8fb9bc5c52d5f8a763595706234114e6bcec9c /src/backend/executor/nodeRecursiveunion.c | |
parent | 3f0b9df88bb33ec52b0af8b11295d256d2011e29 (diff) | |
download | postgresql-1136d81bfa7f902a14fd426a97ecd99381d72953.tar.gz postgresql-1136d81bfa7f902a14fd426a97ecd99381d72953.zip |
AdjustUpgrade.pm should zap test_ext_cine, too.
test_extensions' test_ext_cine extension has the same upgrade hazard
as test_ext7: the regression test leaves it in an updated state
from which no downgrade path to default is provided. This causes
the update_extensions.sql script helpfully provided by pg_upgrade
to fail. So drop it in cross-version-upgrade testing.
Not entirely sure how come I didn't hit this in testing yesterday;
possibly I'd built the upgrade reference databases with
testmodules-install-check disabled.
Backpatch to v10 where this module was introduced.
Diffstat (limited to 'src/backend/executor/nodeRecursiveunion.c')
0 files changed, 0 insertions, 0 deletions