Fix Test Failure in multi-mx in PG17 (#7722)

This PR addresses a regression test failure in the multi-mx feature of Citus with the new PostgreSQL 17 version. The regression was identified during the execution of multi-node tests, specifically targeting compatibility issues introduced with PostgreSQL 17. --------- Co-authored-by: Mehmet YILMAZ <[email protected]> (cherry picked from commit 70cf729)
citusdata · Nov 19, 2024 · d86362d · d86362d
1 parent 3f2823e
commit d86362d
Show file tree

Hide file tree

Showing 12 changed files with 4,047 additions and 21 deletions.
diff --git a/src/test/regress/bin/normalize.sed b/src/test/regress/bin/normalize.sed
@@ -309,3 +309,8 @@ s/permission denied to terminate process/must be a superuser to terminate superu
 s/permission denied to cancel query/must be a superuser to cancel superuser query/g
 
 #endif /* PG_VERSION_NUM < PG_VERSION_16 */
+
+# pg17 changes
+
+# multi_mx_router_planner normalize public.pg_temp_xxxxx
+s/DEBUG:  drop auto-cascades to type public\.pg_temp_[0-9]+/DEBUG:  drop auto-cascades to type public.pg_temp_xxxxx/g
diff --git a/src/test/regress/expected/ch_bench_having_mx.out b/src/test/regress/expected/ch_bench_having_mx.out
@@ -1,3 +1,8 @@
+-- Two alternative test outputs:
+-- ch_bench_having_mx.out for PG16 and before
+-- ch_bench_having_mx_0.out for PG17
+-- related commit
+-- https://github.com/postgres/postgres/commit/fd0398fc
 ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1640000;
 SET citus.shard_replication_factor to 1;
 SET citus.shard_count to 4;