aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2021-03-10 19:00:48 -0800
committerPeter Geoghegan <pg@bowt.ie>2021-03-10 19:00:48 -0800
commit57ae7885cfe7a6301e1fd4b59c2e525ecc35cd55 (patch)
treeacc9b40b55466c9fcfb2fed24ca2a97cdf5d0fc8 /src/backend/parser/parse_utilcmd.c
parent5645a6af70adaaaa485b8568bad9bc7fc130d474 (diff)
downloadpostgresql-57ae7885cfe7a6301e1fd4b59c2e525ecc35cd55.tar.gz
postgresql-57ae7885cfe7a6301e1fd4b59c2e525ecc35cd55.zip
Drop index behind pg_upgrade test issue.
The vacuum_cleanup_index_scale_factor storage parameter was set in a btree index that was previously left behind in the regression test database. As a result, the index gets tested within pg_dump and pg_restore tests, as well as pg_upgrade testing. This won't work when upgrading to Postgres 14, though, because the storage parameter was removed on that version by commit 9f3665fb. Fix the test failure by dropping the index in question. Per buildfarm member crake. Discussion: https://postgr.es/m/CAH2-WzmeXYBWdhF7BMhNjhq9exsk=E1ohqBFAwzPdXJZ1XDMUA@mail.gmail.com Backpatch: 11-12 only
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions