Commit0f1b0c0

committed

Fix duplicated test case in TAP tests of reindexdb

The same test for REINDEX (VERBOSE) was done twice, while it is clearthat the second test should use --concurrently. Issue introduced in5dc92b8, for what looks like a copy-paste mistake.Reviewed-by: Mark DilgerDiscussion:https://postgr.es/m/A7AE97EA-F4B0-4CAB-8FFF-3FECD31F9D63@enterprisedb.comBackpatch-through: 12

1 parent262eb99 commit0f1b0c0Copy full SHA for 0f1b0c0

File tree

-3

lines changed

-3

lines changed

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -64,9 +64,9 @@`
`64`	`64`	`$node->command_fails(['reindexdb','--concurrently','-s','postgres' ],`
`65`	`65`	`'reindex system tables concurrently');`
`66`	`66`	`$node->issues_sql_like(`
`67`		`-['reindexdb','-v','-t','test1','postgres' ],`
`68`		`-qr/statement: REINDEX$VERBOSE$ TABLE public\.test1;/,`
`69`		`-'reindex with verbose output');`
	`67`	`+['reindexdb','--concurrently','-v','-t','test1','postgres' ],`
	`68`	`+qr/statement: REINDEX$VERBOSE$ TABLECONCURRENTLYpublic\.test1;/,`
	`69`	`+'reindex with verbose output concurrently');`
`70`	`70`
`71`	`71`	`# connection strings`
`72`	`72`	`$node->command_ok([qw(reindexdb --echo --table=pg_am dbname=template1)],`

Comments

(0)