parallel_schedule_dump_restore

# ----------
# src/test/regress/parallel_schedule
#
# Most test scripts can be run after running just test_setup and possibly
# create_index.  Exceptions to this rule are documented below.
#
# By convention, we put no more than twenty tests in any one parallel group;
# this limits the number of connections needed to run the tests.
# ----------

# required setup steps
test: test_setup

# ----------
# The first group of parallel tests
# ----------
test: boolean name varchar int2 int4 int8 oid float4 float8 bit numeric uuid enum money rangetypes pg_lsn 

# ----------
# The second group of parallel tests
# multirangetypes depends on rangetypes
# multirangetypes shouldn't run concurrently with type_sanity
# ----------
test: numerology point lseg line box path polygon circle date time timetz timestamp timestamptz interval inet macaddr macaddr8 multirangetypes

# ----------
# Another group of parallel tests
# geometry depends on point, lseg, line, box, path, polygon, circle
# horology depends on date, time, timetz, timestamp, timestamptz, interval
# ----------
test: geometry xid 

# ----------
# Load huge amounts of data
# We should split the data files into single files and then
# execute two copy tests in parallel, to check that copy itself
# is concurrent safe.
# ----------
test: insert insert_conflict

# ----------
# More groups of parallel tests
# Note: many of the tests in later groups depend on create_index
# ----------
test: create_function_c create_misc create_operator create_procedure create_table create_type create_schema
test: create_index create_index_spgist create_view index_including index_including_gist

# ----------
# Another group of parallel tests
# ----------
test: create_aggregate create_function_sql create_cast constraints triggers inherit typed_table updatable_views roleattributes create_am 

# ----------
# sanity_check does a vacuum, affecting the sort order of SELECT *
# results. So it should not run parallel to other tests.
# ----------

# ----------
# Another group of parallel tests
# aggregates depends on create_aggregate
# join depends on create_misc
# ----------
test: select_into case join aggregates random arrays btree_index hash_index namespace 

# ----------
# Another group of parallel tests
# ----------
test: brin gin gist spgist privileges init_privs security_label collate matview replica_identity rowsecurity object_address password identity generated_stored 

# ----------
# Additional BRIN tests
# ----------
test: brin_bloom brin_multi

# ----------
# Another group of parallel tests
# psql depends on create_am
# amutils depends on geometry, create_index_spgist, hash_index, brin
# ----------
test: create_table_like alter_generic alter_operator misc misc_functions collate.utf8 collate.icu.utf8 create_role without_overlaps generated_virtual

# collate.linux.utf8 and collate.icu.utf8 tests cannot be run in parallel with each other
test: rules stats_ext collate.linux.utf8 collate.windows.win1252

# ----------
# Run these alone so they don't run out of parallel workers
# select_parallel depends on create_misc
# ----------
test: write_parallel

# no relation related tests can be put in this group
test: publication subscription

# ----------
# Another group of parallel tests
# select_views depends on create_view
# ----------
test: select_views foreign_key cluster dependency tsearch tsdicts foreign_data indirect_toast 

# ----------
# Another group of parallel tests (JSON related)
# ----------
test: json jsonb sqljson sqljson_queryfuncs sqljson_jsontable

# ----------
# Another group of parallel tests
# with depends on create_misc
# NB: temp.sql does reconnects which transiently use 2 connections,
# so keep this parallel group to at most 19 tests
# ----------
test: limit plpgsql domain rangefuncs conversion alter_table sequence polymorphism rowtypes largeobject with xml

# ----------
# Another group of parallel tests
#
# The stats test resets stats, so nothing else needing stats access can be in
# this group.
# ----------
test: reloptions hash_part indexing partition_info tuplesort compression stats 

# event_trigger depends on create_am and cannot run concurrently with
# any test that runs DDL
# oidjoins is read-only, though, and should run late for best coverage
test: event_trigger

# event_trigger_login cannot run concurrently with any other tests because
# on-login event handling could catch connection of a concurrent test.
test: event_trigger_login

# this test also uses event triggers, so likewise run it by itself
test: fast_default

# run tablespace test at the end because it drops the tablespace created during
# setup that other tests may use.
test: tablespace