2000-09-29 19:17:41 +02:00
# ----------
2010-09-20 22:08:53 +02:00
# src/test/regress/parallel_schedule
2007-08-21 03:11:32 +02:00
#
# 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.
# ----------
2009-08-24 05:10:16 +02:00
# run tablespace by itself, and first, because it forces a checkpoint;
# we'd prefer not to have checkpoints later in the tests because that
# interferes with crash-recovery testing.
test: tablespace
2007-08-21 03:11:32 +02:00
# ----------
# The first group of parallel tests
2000-09-29 19:17:41 +02:00
# ----------
2014-04-08 16:27:56 +02:00
test: boolean char name varchar text int2 int4 int8 oid float4 float8 bit numeric txid uuid enum money rangetypes pg_lsn regproc
2000-09-29 19:17:41 +02:00
# Depends on things setup during char, varchar and text
test: strings
# Depends on int2, int4, int8, float4, float8
test: numerology
# ----------
2007-08-21 03:11:32 +02:00
# The second group of parallel tests
2000-09-29 19:17:41 +02:00
# ----------
2017-03-15 16:16:25 +01:00
test: point lseg line box path polygon circle date time timetz timestamp timestamptz interval abstime reltime tinterval inet macaddr macaddr8 tstypes comments
2000-09-29 19:17:41 +02:00
2007-08-21 03:11:32 +02:00
# ----------
# Another group of parallel tests
# geometry depends on point, lseg, box, path, polygon and circle
# horology depends on interval, timetz, timestamp, timestamptz, reltime and abstime
# ----------
2017-03-12 00:36:50 +01:00
test: geometry horology regex oidjoins type_sanity opr_sanity expressions
2000-09-29 19:17:41 +02:00
# ----------
# These four each depend on the previous one
# ----------
2002-04-05 13:56:55 +02:00
test: insert
Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.
The newly added ON CONFLICT clause allows to specify an alternative to
raising a unique or exclusion constraint violation error when inserting.
ON CONFLICT refers to constraints that can either be specified using a
inference clause (by specifying the columns of a unique constraint) or
by naming a unique or exclusion constraint. DO NOTHING avoids the
constraint violation, without touching the pre-existing row. DO UPDATE
SET ... [WHERE ...] updates the pre-existing tuple, and has access to
both the tuple proposed for insertion and the existing tuple; the
optional WHERE clause can be used to prevent an update from being
executed. The UPDATE SET and WHERE clauses have access to the tuple
proposed for insertion using the "magic" EXCLUDED alias, and to the
pre-existing tuple using the table name or its alias.
This feature is often referred to as upsert.
This is implemented using a new infrastructure called "speculative
insertion". It is an optimistic variant of regular insertion that first
does a pre-check for existing tuples and then attempts an insert. If a
violating tuple was inserted concurrently, the speculatively inserted
tuple is deleted and a new attempt is made. If the pre-check finds a
matching tuple the alternative DO NOTHING or DO UPDATE action is taken.
If the insertion succeeds without detecting a conflict, the tuple is
deemed inserted.
To handle the possible ambiguity between the excluded alias and a table
named excluded, and for convenience with long relation names, INSERT
INTO now can alias its target table.
Bumps catversion as stored rules change.
Author: Peter Geoghegan, with significant contributions from Heikki
Linnakangas and Andres Freund. Testing infrastructure by Jeff Janes.
Reviewed-By: Heikki Linnakangas, Andres Freund, Robert Haas, Simon Riggs,
Dean Rasheed, Stephen Frost and many others.
2015-05-08 05:31:36 +02:00
test: insert_conflict
2000-09-29 19:17:41 +02:00
test: create_function_1
test: create_type
test: create_table
test: create_function_2
# ----------
# Load huge amounts of data
# We should split the data files into single files and then
# execute two copy tests parallel, to check that copy itself
# is concurrent safe.
# ----------
2015-11-27 17:11:22 +01:00
test: copy copyselect copydml
2000-09-29 19:17:41 +02:00
# ----------
2011-11-09 05:05:14 +01:00
# More groups of parallel tests
2000-09-29 19:17:41 +02:00
# ----------
2011-11-09 05:05:14 +01:00
test: create_misc create_operator
# These depend on the above two
2016-04-08 20:52:13 +02:00
test: create_index create_view
2000-09-29 19:17:41 +02:00
2011-11-09 05:05:14 +01:00
# ----------
# Another group of parallel tests
# ----------
2016-03-24 03:01:35 +01:00
test: create_aggregate create_function_3 create_cast constraints triggers inherit create_table_like typed_table vacuum drop_if_exists updatable_views rolenames roleattributes create_am
2011-11-09 05:05:14 +01:00
2000-09-29 19:17:41 +02:00
# ----------
# sanity_check does a vacuum, affecting the sort order of SELECT *
# results. So it should not run parallel to other tests.
# ----------
test: sanity_check
# ----------
# Believe it or not, select creates a table, subsequent
# tests need.
# ----------
test: errors
test: select
2002-08-11 04:06:32 +02:00
ignore: random
2000-09-29 19:17:41 +02:00
# ----------
2007-08-21 03:11:32 +02:00
# Another group of parallel tests
2000-09-29 19:17:41 +02:00
# ----------
2015-01-02 21:09:39 +01:00
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
2000-09-29 19:17:41 +02:00
2011-03-20 19:35:39 +01:00
# ----------
# Another group of parallel tests
# ----------
2017-03-07 13:25:52 +01:00
test: brin gin gist spgist privileges init_privs security_label collate matview lock replica_identity rowsecurity object_address tablesample groupingsets drop_operator large_object password
2012-10-15 18:18:52 +02:00
# ----------
# Another group of parallel tests
# ----------
2017-03-20 17:30:08 +01:00
test: alter_generic alter_operator misc psql async dbsize misc_functions sysviews tsrf tidscan
2011-03-20 19:35:39 +01:00
2010-02-12 18:33:21 +01:00
# rules cannot run concurrently with any test that creates a view
2016-08-22 18:00:00 +02:00
test: rules psql_crosstab amutils
# run by itself so it can run parallel workers
test: select_parallel
2000-09-29 19:17:41 +02:00
2017-01-19 18:00:00 +01:00
# no relation related tests can be put in this group
test: publication subscription
2000-09-29 19:17:41 +02:00
# ----------
2007-08-21 03:11:32 +02:00
# Another group of parallel tests
2000-09-29 19:17:41 +02:00
# ----------
2015-10-07 23:41:45 +02:00
test: select_views portals_p2 foreign_key cluster dependency guc bitmapops combocid tsearch tsdicts foreign_data window xmlmap functional_deps advisory_lock json jsonb json_encoding indirect_toast equivclass
2000-09-29 19:17:41 +02:00
# ----------
2007-08-21 03:11:32 +02:00
# Another group of parallel tests
2008-12-30 18:11:26 +01:00
# NB: temp.sql does a reconnect which transiently uses 2 connections,
# so keep this parallel group to at most 19 tests
2000-09-29 19:17:41 +02:00
# ----------
2012-09-29 05:32:57 +02:00
test: plancache limit plpgsql copy2 temp domain rangefuncs prepare without_oid conversion truncate alter_table sequence polymorphism rowtypes returning largeobject with xml
2004-01-27 01:50:33 +01:00
2014-12-07 16:55:28 +01:00
# event triggers cannot run concurrently with any test that runs DDL
test: event_trigger
2004-01-27 01:50:33 +01:00
# run stats by itself because its delay may be insufficient under heavy load
test: stats