Fix ORDER BY clause in new regression test of REINDEX CONCURRENTLY

michaelpq · michaelpq · commit 5b2945ec0a39 · 2021-02-10T16:59:43.000+09:00
Oversight in bd12080. Reported-by: Justin Pryzby Discussion: https://postgr.es/m/20210210065805.GG20012@telsasoft.com Backpatch-through: 12
diff --git a/src/test/regress/expected/create_index.out b/src/test/regress/expected/create_index.out
@@ -2492,7 +2492,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
diff --git a/src/test/regress/sql/create_index.sql b/src/test/regress/sql/create_index.sql
@@ -1028,7 +1028,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.
