"int" and "int4" are the same datatype. They are mapped to the same early
on, in the parsing stage. For those tests that have been duplicated for
many different datatypes, remove the _int_ variant, leaving just the
_int4_ variant.

We have sufficient coverage for these in the 'geometry' test in the main
test suite. There are no UPDATEs in 'geometry', but that seems
uninteresting; there is no reason to believe that UPDATE on these types
would behave differently from an UPDATE on any other type.

The test descriptions were misleading, BTW. These are not "boundary"
tests, the values used are not close to the min or max values the data
types can represent.

PR pipeline: use 'max_in_flight: 1' and 'version: every' to ensure all PRs flow through the pipeline
Signed-off-by: NJingyi Mei <jmei@pivotal.io>

Signed-off-by: NTom Meyer <tmeyer@pivotal.io>

Signed-off-by: NTom Meyer <tmeyer@pivotal.io>

We have a bunch of existing tests that test whether ORCA falls back. They
set optimizer_log_failure='all' and client_min_messages='log', and grep
the output for "Planner" or "Planner produced plan". That's error-prone.

This new GUC makes that kind of tests easier and more robust. You can
simply set the GUC, and if there are no extra INFO messages in the output,
ORCA didn't fall back.

We had already disabled ORCA for some queries, but the query to estimate
reltuples and relpages still used ORCA. This makes ANALYZE slightly faster
(because ORCA is slow to start up), and avoids spurious messages about
GPORCA falling back when the new optimizer_trace_failure option is used.

Currently, we have a job compile_gpdb_custom_config_centos6 in
pr_pipeline and master that compiles gpdb with a custom config, but the
purpose of this job is unclear. It turns out that this job is for
compiling gpdb the open-source way, so we renamed the job as
compile_gpdb_open_source and changed the name of task yml and scripts.
Signed-off-by: NDavid Sharp <dsharp@pivotal.io>

* Move all the udf_insert_* tests to the main suite.

* Move 'volatilefn_dml_int8' test to the main suite.

* Remove all the other volatilefn_dml_* tests. There's no reason to believe
  that the data types used in the table would make a difference, so keeping
  one variant of this is enough.

* Run behave tests in concourse

* Initial steps to enable us to run behave tests in concourse.
  This will only work for single node behave tests.
Signed-off-by: NChumki Roy <croy@pivotal.io>

Below columns are added:

* rsgid: resgroup id;
* rsgname: resgroup name;
* rsgqueueduration: queued duration in the resgroup;

As resgroup is not fully implemented yet there is only dummy output for
these columns at the moment.

Add view gp_toolkit.gp_resgroup_status for resource group runtime
statistics information, such as cpu usage, memory usage, etc..

Example:

    -- query resource group runtime statistics information
    SELECT * FROM gp_toolkit.gp_resgroup_status;

A helper function pg_resgroup_get_status_kv() is also provided to
collect these information.

A new dir src/backend/utils/resgroup/ is created to hold the resgroup
source code.

As resgroup is not fully implemented yet there is only dummy output for
this view at the moment.

Add view gp_toolkit.gp_resgroup_config for resource group information,
such as concurrency, cpu rate limitation, etc..

Example:

    -- query resource group config information
    SELECT * FROM gp_toolkit.gp_resgroup_config;

docker image jtarchie/pr updated recently, which breaks our git
submodule pulling, fall back to the working tag.
Signed-off-by: NAdam Lee <ali@pivotal.io>
Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>

I'm not how many of these tests are worth keeping at all, but as a first
step, let's get them into the main test suite. The runtime of the parallel
group with these tests is about 1 minute on my laptop.

This is mostly a straightforward move, with mechanical changes removing the
useless TINC tags. However, some tests were marked with the special
"@executemode ORCA_PLANNER_DIFF" tag. The code in __init__.py ran those
tests differently. Normally, you run a test, and comparet the output with
the expected output file. But those ORCA_PLANNER_DIFF tests were run twice,
with and without ORCA, and the results were compared against each other,
instead of the expected output stored in the repository. The expected
outputs of those tests were out of date, you got a different error message
now than what was remembered in the expected output.

Now those tests are run as normal pg_regress tests. I updated the expected
output of those tests to match what you get nowadays.

pg_size_pretty() is completely ordinary and boring function. It doesn't
do database access or anything like that. We can live without testing it
in every possible context.

* dml_boundary_bool seems redundant. We surely have a lot of other tests
  involving boolean columns.
* dml_boundary_char is redundant with the 'char' test in main suite.
* dml_boundary_money was disabled.
* dml_boundary_smallint was redundant with 'int2' test in main suite.
* dml_boundary_integer was redundant with 'int4' test in main suite.
* dml_boundary_bigint was redundant with 'int8' test in main suite.

There are a lot of similar and more interesting tests for direct dispatch
in the main test suite ('direct_dispatch' test, for example).

The negative test cases, like inserting into a randomly distributed table
so that direct dispatch is not possible, were not very interesting, so I
removed them. A mistake in the other direction, i.e. not performing direct
dispatch when we could have, does not lead to incorrect query results, just
slower performance, which is why we need bespoken tests for those. But
if we erroneously do direct dispatch for a query, where it is not legal,
that will lead to incorrect query results, so we should catch those cases
by all the other tests in the test suite.

There was one test case, involving DEFAULTs in the INSERT statement, that
I thought is marginally worth keeping, so added a case for that in
'direct_dispatch' before removing it.

We have sufficient coverage for these in the main regression suite already.

* Partitions are covered by the 'partindex_test', 'partition', and
  'partition1' tests.

* ALTER TABLE on non-partitioned tests are covered in 'alter_table' test.

* SET DISTRIBUTION POLICY is covered by the 'alter_distribution_policy'
  test. It seems unnecessary test so many different data types,
  there is no datatype-specific handling in the set distribution policy
  code.

* Merge recent changes

* Remove examples with deprecated functions

* Move examples using deprecated analytic functions to MADlib doc, and redo with MADlib functions.

* Removes deprecated functions, relocates the unnest() function, and links to MADlib topic.

[ci skip]

This will make the test more reliable, because extra waiting in the relcache
initialization caused some case the segment took longer to recover.

Bad things happen otherwise. One case in point is create database
followed by a crash. Create database requests a checkpoint after
inserting new tuple into pg_database. Crash happens right after
create database commits and before clog update is not flushed to disk.
Relcache initialization before xlog replay will set HEAP_XMIN_INVALID
hint bit in the newly created database's tuple because clog did not
report the xmin as committed.

The FileRep processes including:
- recovery process
- resync manager process
- resync worker process

The need for heap access methods before xlog replay is removed by commit
e2d6aa1481f6cdbd846d4b17b68eb4387dae9211. This commit simply moves the
relcache initialization to pass4, where it is really needed.

Do not bother to remove relcache init file at the end of crash recovery pass2.

Error out if relation cache initialized at wrong time.

Handling of gp_reject_internal_tcp_conn was defined twice in the
GUC file, remove one.

These GUCs were all only defined in the GUC file and completely
Aunused in the code, probably leftovers from when the original
code using them was removed. Now remove the GUCs.

Debug_gp_relation_node_fetch_wait_for_debugging was added to assist
debugging an issue in the RelationFetchGpRelationNodeForXLog recursion
guard. The bug was not reproduced but the GUC was left in when the
ticket was closed so remove. If we need to debug this in the future
we should add something back then.

Fix a common typo in the user facing documentation.

The error messages are developer or debug facing, no reason to
believe this will break anyones regexing of logfiles in prod.

* Update regex to reflect output change [#140454709]

`pg_lock_status` changed output format.

We cannot assume we are running in a special environment that is always
in -8 time zone without DST. Making such setting explicit to make tests
portable.

Unskipping test as they will succeed now.