external
/
citus
mirror of https://github.com/citusdata/citus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1426 from citusdata/better_comment_for_tests 

Add comment to subquery regression test file
pull/1429/head
Önder Kalacı 2017-05-22 11:12:20 +03:00 committed by GitHub
parent 7d28423891 757f5be858
commit 1ea96b626b
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/test/regress/expected/multi_subquery_behavioral_analytics.out
View File

@ -3,9 +3,11 @@
-- regression tests to cover more cases -- regression tests to cover more cases
-- the tables that are used depends to multi_insert_select_behavioral_analytics_create_table.sql -- the tables that are used depends to multi_insert_select_behavioral_analytics_create_table.sql
-- --
-- We don't need shard id sequence here, so commented out to prevent conflicts with concurrent tests --- We don't need shard id sequence here given that we're not creating any shards, so not writing it at all
-- ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1430000; -- The following line is intended to force Citus to NOT use router planner for the tests in this
-- ALTER SEQUENCE pg_catalog.pg_dist_jobid_seq RESTART 1430000; -- file. The motivation for doing this is to make sure that single-task queries can be planned
-- by non-router code-paths. Thus, this flag should NOT be used in production. Otherwise, the actual
-- router queries would fail.
SET citus.enable_router_execution TO FALSE; SET citus.enable_router_execution TO FALSE;
------------------------------------ ------------------------------------
-- Vanilla funnel query -- Vanilla funnel query

8
src/test/regress/sql/multi_subquery_behavioral_analytics.sql
View File

@ -4,10 +4,12 @@
-- the tables that are used depends to multi_insert_select_behavioral_analytics_create_table.sql -- the tables that are used depends to multi_insert_select_behavioral_analytics_create_table.sql
-- --
-- We don't need shard id sequence here, so commented out to prevent conflicts with concurrent tests --- We don't need shard id sequence here given that we're not creating any shards, so not writing it at all
-- ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1430000;
-- ALTER SEQUENCE pg_catalog.pg_dist_jobid_seq RESTART 1430000;
-- The following line is intended to force Citus to NOT use router planner for the tests in this
-- file. The motivation for doing this is to make sure that single-task queries can be planned
-- by non-router code-paths. Thus, this flag should NOT be used in production. Otherwise, the actual
-- router queries would fail.
SET citus.enable_router_execution TO FALSE; SET citus.enable_router_execution TO FALSE;
------------------------------------ ------------------------------------