Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 57ae788

Browse files
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 9f3665f. 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
1 parent 5645a6a commit 57ae788

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed

src/test/regress/expected/btree_index.out

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -312,6 +312,7 @@ select reloptions from pg_class WHERE oid = 'btree_idx1'::regclass;
312312
{vacuum_cleanup_index_scale_factor=70.0}
313313
(1 row)
314314

315+
drop index btree_idx1;
315316
--
316317
-- Test for multilevel page deletion
317318
--

src/test/regress/sql/btree_index.sql

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,7 @@ create index btree_idx_err on btree_test(a) with (vacuum_cleanup_index_scale_fac
140140
-- Simple ALTER INDEX
141141
alter index btree_idx1 set (vacuum_cleanup_index_scale_factor = 70.0);
142142
select reloptions from pg_class WHERE oid = 'btree_idx1'::regclass;
143+
drop index btree_idx1;
143144

144145
--
145146
-- Test for multilevel page deletion

0 commit comments

Comments
 (0)