56 Commits (ee0cd756485c32bf630a32a38c9e465d95aecabc)

Author	SHA1	Message	Date
Hadi Moshayedi	dda53a0bba	GUC for replicate reference tables on activate.	2020-04-08 12:42:45 -07:00
Hadi Moshayedi	0758a81287	Prevent reference tables being dropped when replicating reference tables	2020-04-08 12:41:36 -07:00
SaitTalhaNisanci	5bf9f32dd3	disable one of deadlock detection test (#3682) ... It seems that one of the deadlock detection tests fails way too often in our CI. The difference is only ordering. Currently it seems that it is a good idea to disable this test for the sake of development.	2020-03-31 19:47:58 +03:00
Hadi Moshayedi	b46b9a68ae	Tests for master_copy_shard_placement	2020-03-23 08:33:55 -07:00
Hadi Moshayedi	3258d87f3e	Isolation tests for INSERT/SELECT repartition	2020-01-16 23:24:52 -08:00
SaitTalhaNisanci	8e5041885d	Refactor isolation tests (#3062) ... Currently in mx isolation tests the setup is the same except the creation of tables. Isolation framework lets us define multiple `setup` stages, therefore I thought that we can put the `mx_setup` to one file and prepend this prior to running tests. How the structure works: - cpp is used before running isolation tests to preprocess spec files. This way we can include any file we want to. Currently this is used to include mx common part. - spec files are put to `/build/specs` for clear separation between generated files and template files - a symbolic link is created for `/expected` in `build/expected/`. - when running isolation tests, as the `inputdir`, `build` is passed so it runs the spec files from `build/specs` and checks the expected output from `build/expected`. `/specs` is renamed as `/spec` because postgres first look at the `specs` file under current directory, so this is renamed to avoid that since we are running the isolation tests from `build/specs` now. Note: now we use `//` instead of `#` in comments in spec files, because cpp interprets `#` as a directive and it ignores `//`.	2019-12-10 16:12:54 +01:00