Fix ORDER BY clause in new regression test of REINDEX CONCURRENTLY

Oversight in bd12080.

Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/20210210065805.GG20012@telsasoft.com
Backpatch-through: 12
This commit is contained in:
Michael Paquier 2021-02-10 16:59:04 +09:00
parent 092b785fad
commit 4f47260050
2 changed files with 2 additions and 2 deletions

View File

@ -2645,7 +2645,7 @@ SELECT attrelid::regclass, attnum, attstattarget
'concur_exprs_index_expr'::regclass,
'concur_exprs_index_pred'::regclass,
'concur_exprs_index_pred_2'::regclass)
ORDER BY 'concur_exprs_index_expr'::regclass::text, attnum;
ORDER BY attrelid::regclass::text, attnum;
attrelid | attnum | attstattarget
---------------------------+--------+---------------
concur_exprs_index_expr | 1 | 100

View File

@ -1110,7 +1110,7 @@ SELECT attrelid::regclass, attnum, attstattarget
'concur_exprs_index_expr'::regclass,
'concur_exprs_index_pred'::regclass,
'concur_exprs_index_pred_2'::regclass)
ORDER BY 'concur_exprs_index_expr'::regclass::text, attnum;
ORDER BY attrelid::regclass::text, attnum;
DROP TABLE concur_exprs_tab;
-- Temporary tables and on-commit actions, where CONCURRENTLY is ignored.