From b7f3e1e7660426f86b794985842c5d5334d9e1f0 Mon Sep 17 00:00:00 2001 From: Burak Velioglu Date: Thu, 13 Jan 2022 15:22:36 +0300 Subject: [PATCH] Fix multi partitioning test --- src/test/regress/expected/multi_partitioning.out | 4 ++-- src/test/regress/sql/multi_partitioning.sql | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/test/regress/expected/multi_partitioning.out b/src/test/regress/expected/multi_partitioning.out index 1b13f09f2..a2c03ef7a 100644 --- a/src/test/regress/expected/multi_partitioning.out +++ b/src/test/regress/expected/multi_partitioning.out @@ -4301,8 +4301,8 @@ WHERE schemaname = 'partitioning_schema' AND tablename ilike '%part_table_with_% (2 rows) -- should work properly - no names clashes -SELECT citus_activate_node('localhost', :worker_1_port); - citus_activate_node +SELECT 1 FROM citus_activate_node('localhost', :worker_1_port); + ?column? --------------------------------------------------------------------- 1 (1 row) diff --git a/src/test/regress/sql/multi_partitioning.sql b/src/test/regress/sql/multi_partitioning.sql index b640d13b3..91bbc180b 100644 --- a/src/test/regress/sql/multi_partitioning.sql +++ b/src/test/regress/sql/multi_partitioning.sql @@ -1992,7 +1992,7 @@ SELECT tablename, indexname FROM pg_indexes WHERE schemaname = 'partitioning_schema' AND tablename ilike '%part_table_with_%' ORDER BY 1, 2; -- should work properly - no names clashes -SELECT citus_activate_node('localhost', :worker_1_port); +SELECT 1 FROM citus_activate_node('localhost', :worker_1_port); \c - - - :worker_1_port -- check that indexes are named properly