aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-01-17 16:00:39 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2023-01-17 16:00:39 -0500
commit3a36ca03e423ad1e2c9f19cd0da5e7dedb48734e (patch)
tree0609ab08f4c7bdf829a530797b793436cbcacde6 /contrib/postgres_fdw/postgres_fdw.c
parent2a1d7071c4ed750abb8b39436bb89c7d152bddb8 (diff)
downloadpostgresql-3a36ca03e423ad1e2c9f19cd0da5e7dedb48734e.tar.gz
postgresql-3a36ca03e423ad1e2c9f19cd0da5e7dedb48734e.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 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions