Adding sha256 as an additional validation method since md5 is not
supported with FIPS mode enabled. Sha256 in the database requires
pgcrypto so we check if the source and destination system have pgcrypto
installed.
Signed-off-by: NChris Hajas <chajas@pivotal.io>

* resgroup: provide helper function to wakeup a proc.
* resgroup: provide helper function to check resWaiting.
* resgroup: refine the logic in ResGroupWaitCancel().
* resgroup: error out in ResGroupHashFind() directly.
* resgroup: error out in ResGroupHashRemove() directly.
* resgroup: add an arg `grant` in wakeupSlots().
* resgroup: move resWaiting updates into WaitQueue helper funcs.
* resgroup: cleanup the duplicate wakeup logic in ResGroupSlotRelease().
* resgroup: fix typo in function name groupAssignChunks().
* resgroup: rename groupAssignChunks() to groupRebalanceQuota().
* resgroup: polish comments for groupApplyMemCaps().
* resgroup: add comments for ResGroup{Caps,Opts}.
* resgroup: cleanup obsolete declarations in resgroup.h
* resgroup: use int32 instead of uint32 for self->memUsage.
* resgroup: correct the slot cleanup in ResGroupWaitCancel().
* resgroup: do not error out in transaction callbacks.

These tables seem dead and were only used before 4.0 era, hence removing them
now from catalog.

The runaway query TINC tests occasionally encounter issues where a
gpstop -ar is not successfull because of open connections. This commit
ensures that at the least gpstop will always restart gpdb.
Signed-off-by: NEkta Khanna <ekhanna@pivotal.io>

This reverts commit e449b1e0.

The NetBackup server has been failing in the first backup run after the
client is set up. We have not been able to discover the cause yet.
We are adding a dummy test where we don't check the return code so that
the rest of the tests will pass.
Signed-off-by: NChris Hajas <chajas@pivotal.io>

GPOS using GPDB for memory allocation is still a feature hidden behind a
GUC and requires more performance testing to be considered for the
default allocation behavior of GPOS. For now it can be ignored from
determing if a build of GPDB is release worthy

configure requires libcurl when pxf is enabled, it's not needed
for resource group regression tests, so disable it.

Previously every resource group has its own slot pool, each with size of 'MaxConnection'.
In order to reduce memory usage, implement a slot pool shared by all resource groups.

In addition, free slots in the slot pool are organized as a free list to optimize alloc/free
operations.

functions

In copyFuncs(), the fallthrough for SpecialJoinInfo was unintentionally
done as a part of subselect merge.  This commit fixes that along with
adding support for new fields in copyFuncs(), outFunc() and equalFunc()

[Ref #151491231]
Signed-off-by: NDhanashree Kashid <dkashid@pivotal.io>

Previously this test's result and plan was wrong. Now, Orca is fixed to
produce a valid plan along with the correct result.

Bump Orca version to 2.46.3

The glob syntax used to validate filenames for segment dump filenames
in the "old" backup format is only correct for single-digit dbids, as
it assumes the use of regex syntax that glob doesn't actually support.

This commit modifies get_filename_for_content to glob for all dump
files present and then explicitly match the expected filenames with a
regular expression.

It also modifies generate_filename to account for files created on a
standby master, which was not correctly handled previously.

Some environment variables passed through the pipeline YAML were not
being passed to the test run (e.g. WITH_MIRRORS=false). Removing the
full login flag of su fixes the issue.

This should speed up the tests a bit, since they are currently spending a significant amount of time in createdb statements.

* Enable PXF by default for GPDB builds

* Disable pxf wherever libcurl is disabled

- instead of trying to keep GPDB readme in sync with GPORCA readme, just refer to it

- fixes cd path
- removes macOS warning that is not currently an issue
- treats comment like other readme comments

After 7e268107 started seeing warnings like
------------------
cdbgroup.c:1478:68: warning: expression which evaluates to zero treated as a null pointer constant of type 'List *' (aka 'struct List *') [-Wnon-literal-null-conversion]
                result_plan = (Plan*)make_motion_gather_to_QE(root, result_plan, false);
                                                                                 ^~~~~
------------------

After commit 1822c826 started seeing bunch of
warnings like
-------------------------------------------
memaccounting.c:247:1: warning: no previous prototype for function 'MemoryAccounting_DeclareDone' [-Wmissing-prototypes]
MemoryAccounting_DeclareDone()
^
../../../../src/include/utils/memaccounting.h:238:1: note: this declaration is not a prototype; add 'void' to make it a prototype for a zero-parameter function
MemoryAccounting_DeclareDone();
^
                             void
memaccounting.c:263:1: warning: no previous prototype for function 'MemoryAccounting_RequestQuotaIncrease' [-Wmissing-prototypes]
MemoryAccounting_RequestQuotaIncrease()
^
../../../../src/include/utils/memaccounting.h:241:1: note: this declaration is not a prototype; add 'void' to make it a prototype for a zero-parameter function
MemoryAccounting_RequestQuotaIncrease();
^
                                      void
2 warnings generated.
ext_alloc.c:35:1: warning: no previous prototype for function 'Ext_OptimizerAlloc' [-Wmissing-prototypes]
Ext_OptimizerAlloc(size_t size)
^
ext_alloc.c:50:17: warning: unused variable 'account' [-Wunused-variable]
        MemoryAccount *account = MemoryAccounting_ConvertIdToAccount(ActiveMemoryAccountId);
                       ^
ext_alloc.c:48:1: warning: no previous prototype for function 'Ext_OptimizerFree' [-Wmissing-prototypes]
Ext_OptimizerFree(void *ptr)
^
ext_alloc.c:59:1: warning: no previous prototype for function 'GetOptimizerOutstandingMemoryBalance' [-Wmissing-prototypes]
GetOptimizerOutstandingMemoryBalance()
^
-------------------------------------------

As part of commit efed2fcc new walrep state was
added 'n' (not-in-sync). The toolkit function gp_pgdatabase__() needs to be
modified as well to check for that state.

Original code not using #defines but direct characters like 's', 'c' makes it
very tricky find stuff in code. Hopefully, future chnages would be easy to spot
and make.

QE detach resource group slot at the end of transaction, the
last QE of the slot release the slot, and release the overused
memory if resource group config has been changed.

commit 07b9936a
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Fri Feb 27 23:30:29 2009 +0000

    Temporarily (I hope) disable flattening of IN/EXISTS sublinks that are within
    the ON clause of an outer join.  Doing so is semantically correct but results
    in de-optimizing queries that were structured to take advantage of the sublink
    style of execution, as seen in recent complaint from Kevin Grittner.  Since
    the user can get the other behavior by reorganizing his query, having the
    flattening happen automatically is just a convenience, and that doesn't
    justify breaking existing applications.  Eventually it would be nice to
    re-enable this, but that seems to require a significantly different approach
    to outer joins in the executor.

Added relevant test case.
Signed-off-by: NDhanashree Kashid <dkashid@pivotal.io>

Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Tue Jul 8 14:03:32 2014 -0400

    While the x output of "select x from t group by x" can be presumed unique,
    this does not hold for "select x, generate_series(1,10) from t group by x",
    because we may expand the set-returning function after the grouping step.
    (Perhaps that should be re-thought; but considering all the other oddities
    involved with SRFs in targetlists, it seems unlikely we'll change it.)
    Put a check in query_is_distinct_for() so it's not fooled by such cases.

    Back-patch to all supported branches.

    David Rowley

(cherry picked from commit 2e7469dc8b3bac4fe0f9bd042aaf802132efde85)

Signed-off-by: NJemish Patel <jpatel@pivotal.io>

Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Tue Dec 10 16:10:36 2013 -0500

An expression such as WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)
could produce an invalid plan that results in a crash at execution time,
if the planner attempts to flatten the outer IN into a semi-join.
This happens because convert_testexpr() was not expecting any nested
SubLinks and would wrongly replace any PARAM_SUBLINK Params belonging
to the inner SubLink.  (I think the comment denying that this case could
happen was wrong when written; it's certainly been wrong for quite a long
time, since very early versions of the semijoin flattening logic.)

Per report from Teodor Sigaev.  Back-patch to all supported branches.

(cherry picked from commit 884c6384a2db34f6a65573e6bfd4b71dfba0de90)

commit 0a0ca1cb18a34e92ab549df171e174dcce7bf7a3
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Sat Mar 24 16:22:00 2012 -0400

    Fix planner's handling of outer PlaceHolderVars within subqueries.

    For some reason, in the original coding of the PlaceHolderVar mechanism
    I had supposed that PlaceHolderVars couldn't propagate into subqueries.
    That is of course entirely possible.  When it happens, we need to treat
    an outer-level PlaceHolderVar much like an outer Var or Aggref, that is
    SS_replace_correlation_vars() needs to replace the PlaceHolderVar with
    a Param, and then when building the finished SubPlan we have to provide
    the PlaceHolderVar expression as an actual parameter for the SubPlan.
    The handling of the contained expression is a bit delicate but it can be
    treated exactly like an Aggref's expression.

    In addition to the missing logic in subselect.c, prepjointree.c was failing
    to search subqueries for PlaceHolderVars that need their relids adjusted
    during subquery pullup.  It looks like everyplace else that touches
    PlaceHolderVars got it right, though.

    Per report from Mark Murawski.  In 9.1 and HEAD, queries affected by this
    oversight would fail with "ERROR: Upper-level PlaceHolderVar found where
    not expected".  But in 9.0 and 8.4, you'd silently get possibly-wrong
    answers, since the value transmitted into the subquery wouldn't go to null
    when it should.