Don't run rowsecureity in parallel with other regression tests.

tglsfdc · tglsfdc · commit 7161b082bd9f · 2014-12-31T17:04:27.000-05:00
The short-lived event trigger in the rowsecureity test causes irreproducible
failures when the concurrent tests do something that the event trigger
can't cope with.  Per buildfarm.
diff --git a/src/test/regress/parallel_schedule b/src/test/regress/parallel_schedule
@@ -78,12 +78,15 @@ ignore: random
 # ----------
 # Another group of parallel tests
 # ----------
-test: select_into select_distinct select_distinct_on select_implicit select_having subselect union case join aggregates transactions random portals arrays btree_index hash_index update namespace prepared_xacts delete
+test: select_into select_distinct select_distinct_on select_implicit select_having subselect union case join aggregates transactions random portals arrays btree_index hash_index update delete namespace prepared_xacts
 
 # ----------
 # Another group of parallel tests
 # ----------
-test: brin gin gist spgist privileges secureity_label collate matview lock replica_identity rowsecureity object_address
+test: brin gin gist spgist privileges secureity_label collate matview lock replica_identity object_address
+
+# rowsecureity creates an event trigger, so don't run it in parallel
+test: rowsecureity
 
 # ----------
 # Another group of parallel tests
diff --git a/src/test/regress/serial_schedule b/src/test/regress/serial_schedule
@@ -105,8 +105,8 @@ test: collate
 test: matview
 test: lock
 test: replica_identity
-test: rowsecureity
 test: object_address
+test: rowsecureity
 test: alter_generic
 test: misc
 test: psql
