4 Commits (386d2567d4fe763a6cc93d65a97b3a24ffc641e1)

Author	SHA1	Message	Date
Marco Slot	89eb833375	Use citus.next_shard_id where practical in regression tests	2017-11-15 10:12:05 +01:00
Marco Slot	f838c83809	Remove redundant pg_dist_jobid_seq restarts in tests	2017-04-18 11:42:32 +02:00
Eren	5512bb359a	Set Explicit ShardId/JobId In Regression Tests ... Fixes #271 This change sets ShardIds and JobIds for each test case. Before this change, when a new test that somehow increments Job or Shard IDs is added, then the tests after the new test should be updated. ShardID and JobID sequences are set at the beginning of each file with the following commands: ``` ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 290000; ALTER SEQUENCE pg_catalog.pg_dist_jobid_seq RESTART 290000; ``` ShardIds and JobIds are multiples of 10000. Exceptions are: - multi_large_shardid: shardid and jobid sequences are set to much larger values - multi_fdw_large_shardid: same as above - multi_join_pruning: Causes a race condition with multi_hash_pruning since they are run in parallel.	2016-06-07 14:32:44 +03:00
Onder Kalaci	136306a1fe	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00