greenplum_schedule

# Greenplum-specific tests
#
# The order of the tests is fairly random, but there are a couple of things
# to consider when placing a new test:
#
# * Keep long-running tests in the same group with other tests with a similar
#   runtime. That way, on a multi-processor system, the tests will finish
#   roughly at the same time, which maximizes parallelism.
# * Keep tests together with other tests for similar functionality.
# * There are some dependencies between tests, and some tests cannot run
#   in parallel with other tests.
# * The maximum size of a group is about 20, like in the Postgres
#   parallel_schedule. However, some queries can dispatch a lot of workers
#   to the segments, and therefore has to run in smaller groups to avoid
#   hitting max_connections limit on segments.
#

ignore: leastsquares
test: opr_sanity_gp decode_expr bitmapscan bitmapscan_ao case_gp limit_gp notin percentile naivebayes join_gp union_gp gpcopy gp_create_table
test: filter gpctas gpdist matrix toast sublink table_functions olap_setup complex opclass_ddl bitmap_index information_schema
test: indexjoin as_alias regex_gp gpparams with_clause transient_types

test: dispatch

# 'segspace' relies on the segment spill space to be 0, and uses fault injectors
# so it needs to be in a group by itself
test: segspace

# 'query_finish_pending' sets QueryFinishPending flag to true during query execution using fault injectors
# so it needs to be in a group by itself
test: query_finish_pending

test: gpdiffcheck gptokencheck gp_hashagg sequence_gp tidscan co_nestloop_idxscan

test: rangefuncs_cdb gp_dqa subselect_gp subselect_gp2 distributed_transactions olap_group olap_window_seq partition1 sirv_functions

# 'partition' runs for a long time, so try to keep it together with other
# long-running tests. Unfortunately, 'partition' also assumes that there
# are no other partitioned tables present in the database, so it cannot run
# in parallel with tests that use partitions.
test: partition appendonly alter_distpol_dropped
# 'partition_locking' gets confused if other backends run concurrently and
# hold locks.
test: partition_locking
test: vacuum_gp

# FIXME: Temporarily disabled, because it trips an assertion. It's probably
# harmless, but need to investigate and fix. Also, the number of errors put
# in the error table, and hence the output, varies between runs.
#test: sreh

# Disabled tests. XXX: Why are these disabled?
#test: olap_window
#test: tpch500GB
#ignore: dpe

# FIXME: These tests no longer work, because they try to set
# gp_interconnect_type, which doesn't work:
# ERROR:  parameter "gp_interconnect_type" cannot be set after connection start

ignore: gp_portal_error
test: external_table partition_indexing column_compression eagerfree mapred gpdtm_plpgsql alter_table_aocs alter_table_ao alter_distribution_policy ic aoco_privileges
ignore: icudp_full
test: aocs

test: resource_queue
# gp_toolkit performs a vacuum and checks that it truncated the relation. That
# might not happen if other backends are holding transactions open, preventing
# vacuum from removing dead tuples.
test: gp_toolkit

test: filespace trig auth_constraint role rle portals_updatable plpgsql_cache timeseries resource_queue_function pg_stat_last_operation gp_numeric_agg partindex_test direct_dispatch partition_pruning_with_fn dsp

# direct dispatch tests
test: bfv_dd bfv_dd_multicolumn bfv_dd_types

test: catalog bfv_catalog bfv_index bfv_olap bfv_aggregate bfv_partition DML_over_joins gp_optimizer bfv_statistic
 
test: aggregate_with_groupingsets 

test: nested_case_null

test: bfv_cte bfv_joins bfv_subquery bfv_planner bfv_legacy

test: qp_olap_mdqa qp_misc

test: qp_misc_jiras qp_with_clause qp_executor qp_olap_windowerr qp_olap_window qp_derived_table qp_bitmapscan
test: qp_functions qp_misc_rio_join_small qp_misc_rio qp_correlated_query qp_targeted_dispatch qp_gist_indexes2 qp_gist_indexes3 qp_gist_indexes4 qp_query_execution

test: qp_dpe qp_subquery qp_functions_idf qp_regexp qp_resource_queue

test: olap_setup
test: qp_olap_group

ignore: tpch500GB_orca

# XXX: This test depends on libgpoptudfs library, which includes ORCA helper
# functions from src/backend/gpopt/utils/funcs.cpp. But those functions are
# built into the backend directly, so what's the point of that? Anyhow, the
# test is disabled for now..
#test: orca_udfs

# Tests for "compaction", i.e. VACUUM, of updatable append-only tables
test: uao_compaction/full uao_compaction/outdated_partialindex uao_compaction/drop_column_update uao_compaction/eof_truncate uao_compaction/basic uao_compaction/outdatedindex uao_compaction/update_toast uao_compaction/outdatedindex_abort uao_compaction/delete_toast uao_compaction/alter_table_analyze uao_compaction/full_eof_truncate uao_compaction/full_threshold
# TODO find why these tests fail in parellel, for now keeping them sequential
test: uao_compaction/full_stats
test: uao_compaction/stats
test: uao_compaction/threshold
test: uao_compaction/index_stats
test: uao_compaction/index
test: uao_compaction/drop_column
test: uao_compaction/index2

# Tests for "compaction", i.e. VACUUM, of updatable append-only column oriented tables
test: uaocs_compaction/alter_table_analyze uaocs_compaction/basic uaocs_compaction/drop_column_update uaocs_compaction/eof_truncate uaocs_compaction/full uaocs_compaction/full_eof_truncate uaocs_compaction/full_threshold uaocs_compaction/outdated_partialindex uaocs_compaction/outdatedindex uaocs_compaction/outdatedindex_abort
# TODO find why these tests fail in parellel, for now keeping them sequential
test: uaocs_compaction/full_stats
test: uaocs_compaction/stats
test: uaocs_compaction/threshold
test: uaocs_compaction/index_stats
test: uaocs_compaction/index
test: uaocs_compaction/drop_column
# end of tests