| commit | 3a36ca03e423ad1e2c9f19cd0da5e7dedb48734e | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Tue, 17 Jan 2023 21:00:39 +0000 (17 16:00 -0500) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Tue, 17 Jan 2023 21:00:39 +0000 (17 16:00 -0500) | ||
| tree | 0609ab08f4c7bdf829a530797b793436cbcacde6 | treesnapshot (tar.gz zip) |
| parent | 2a1d7071c4ed750abb8b39436bb89c7d152bddb8 | commitdiff |
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.
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.
| src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | diffblobblamehistory |