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
|
|
|
# ----------
|
2019-03-12 03:44:28 +01:00
|
|
|
test: point lseg line box path polygon circle date time timetz timestamp timestamptz interval inet macaddr macaddr8 tstypes fsm
|
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
|
2018-09-29 00:21:48 +02:00
|
|
|
# horology depends on interval, timetz, timestamp, timestamptz
|
2007-08-21 03:11:32 +02:00
|
|
|
# ----------
|
Add testing to detect errors of omission in "pin" dependency creation.
It's essential that initdb.c's setup_depend() scan each system catalog
that could contain objects that need to have "p" (pin) entries in pg_depend
or pg_shdepend. Forgetting to add that, either when a catalog is first
invented or when it first acquires DATA() entries, is an obvious bug
hazard. We can detect such omissions at reasonable cost by probing every
OID-containing system catalog to see whether the lowest-numbered OID in it
is pinned. If so, the catalog must have been properly accounted for in
setup_depend(). If the lowest OID is above FirstNormalObjectId then the
catalog must have been empty at the end of initdb, so it doesn't matter.
There are a small number of catalogs whose first entry is made later in
initdb than setup_depend(), resulting in nonempty expected output of the
test, but these can be manually inspected to see that they are OK. Any
future mistake of this ilk will manifest as a new entry in the test's
output.
Since pg_conversion is already in the test's output, add it to the set of
catalogs scanned by setup_depend(). That has no effect today (hence, no
catversion bump here) but it will protect us if we ever do add pin-worthy
conversions.
This test is very much like the catalog sanity checks embodied in
opr_sanity.sql and type_sanity.sql, but testing pg_depend doesn't seem to
fit naturally into either of those scripts' charters. Hence, invent a new
test script misc_sanity.sql, which can be a home for this as well as tests
on any other catalogs we might want in future.
Discussion: https://postgr.es/m/8068.1498155068@sss.pgh.pa.us
2017-06-23 17:03:04 +02:00
|
|
|
test: geometry horology regex oidjoins type_sanity opr_sanity misc_sanity comments 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
|
|
|
# ----------
|
2017-11-30 14:46:13 +01:00
|
|
|
test: create_misc create_operator create_procedure
|
2011-11-09 05:05:14 +01:00
|
|
|
# These depend on the above two
|
2019-03-10 09:36:47 +01:00
|
|
|
test: create_index create_view index_including index_including_gist
|
2000-09-29 19:17:41 +02:00
|
|
|
|
2011-11-09 05:05:14 +01:00
|
|
|
# ----------
|
|
|
|
# Another group of parallel tests
|
|
|
|
# ----------
|
2019-03-15 00:16:45 +01:00
|
|
|
test: create_aggregate create_function_3 create_cast constraints triggers inherit typed_table vacuum drop_if_exists updatable_views rolenames roleattributes create_am hash_func
|
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
|
|
|
|
# ----------
|
2019-03-15 00:16:45 +01:00
|
|
|
test: brin gin gist spgist privileges init_privs security_label collate matview lock replica_identity rowsecurity object_address tablesample groupingsets drop_operator password identity
|
2012-10-15 18:18:52 +02:00
|
|
|
|
|
|
|
# ----------
|
|
|
|
# Another group of parallel tests
|
|
|
|
# ----------
|
2019-03-15 00:16:45 +01:00
|
|
|
test: create_table_like alter_generic alter_operator misc psql async dbsize misc_functions sysviews tsrf tidscan stats_ext
|
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
|
2017-10-05 17:34:38 +02:00
|
|
|
test: write_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
|
|
|
# ----------
|
2017-10-07 19:19:13 +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
|
Basic partition-wise join functionality.
Instead of joining two partitioned tables in their entirety we can, if
it is an equi-join on the partition keys, join the matching partitions
individually. This involves teaching the planner about "other join"
rels, which are related to regular join rels in the same way that
other member rels are related to baserels. This can use significantly
more CPU time and memory than regular join planning, because there may
now be a set of "other" rels not only for every base relation but also
for every join relation. In most practical cases, this probably
shouldn't be a problem, because (1) it's probably unusual to join many
tables each with many partitions using the partition keys for all
joins and (2) if you do that scenario then you probably have a big
enough machine to handle the increased memory cost of planning and (3)
the resulting plan is highly likely to be better, so what you spend in
planning you'll make up on the execution side. All the same, for now,
turn this feature off by default.
Currently, we can only perform joins between two tables whose
partitioning schemes are absolutely identical. It would be nice to
cope with other scenarios, such as extra partitions on one side or the
other with no match on the other side, but that will have to wait for
a future patch.
Ashutosh Bapat, reviewed and tested by Rajkumar Raghuwanshi, Amit
Langote, Rafia Sabih, Thomas Munro, Dilip Kumar, Antonin Houska, Amit
Khandekar, and by me. A few final adjustments by me.
Discussion: http://postgr.es/m/CAFjFpRfQ8GrQvzp3jA2wnLqrHmaXna-urjm_UY9BqXj=EaDTSA@mail.gmail.com
Discussion: http://postgr.es/m/CAFjFpRcitjfrULr5jfuKWRPsGUX0LQ0k8-yG0Qw2+1LBGNpMdw@mail.gmail.com
2017-10-06 17:11:10 +02:00
|
|
|
|
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
|
|
|
# ----------
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
test: plancache limit plpgsql copy2 temp domain rangefuncs prepare conversion truncate alter_table sequence polymorphism rowtypes returning largeobject with xml
|
2004-01-27 01:50:33 +01:00
|
|
|
|
2017-04-06 14:33:16 +02:00
|
|
|
# ----------
|
|
|
|
# Another group of parallel tests
|
|
|
|
# ----------
|
2019-03-15 00:16:45 +01:00
|
|
|
test: partition_join partition_prune reloptions hash_part indexing partition_aggregate partition_info
|
2017-04-06 14:33:16 +02:00
|
|
|
|
2014-12-07 16:55:28 +01:00
|
|
|
# event triggers cannot run concurrently with any test that runs DDL
|
|
|
|
test: event_trigger
|
2018-04-20 23:27:56 +02:00
|
|
|
# this test also uses event triggers, so likewise run it by itself
|
|
|
|
test: fast_default
|
2014-12-07 16:55:28 +01:00
|
|
|
|
2004-01-27 01:50:33 +01:00
|
|
|
# run stats by itself because its delay may be insufficient under heavy load
|
|
|
|
test: stats
|