aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.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:01:06 -0500
commit58393ea56ef8e75bcd60af1f88d0a81b1d8e21eb (patch)
tree303fcb509df5978e30e625e125e34f42be61a069 /src/backend/parser/parse_expr.c
parent0e4d38100acb90d93e68694674050f4cebdd816a (diff)
downloadpostgresql-58393ea56ef8e75bcd60af1f88d0a81b1d8e21eb.tar.gz
postgresql-58393ea56ef8e75bcd60af1f88d0a81b1d8e21eb.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/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions