Currently, isolation2 vacuum_cleanup test was using base AO/CO tables for
validating if age drops down. Actaully the test should check auxiliary
tables. As anyways relfrozenxid doesn't carry any weigth for AO/CO base table.

AO and CO tables never store transactionIds and persistent table always have
tuples with FrozenXid only. Hence these tables should not have valid
relfrozenxid, hence also should not matter for age calculation. Persistent
tables are currently skipped internally from `datfrozenxid` calculation but
still contained valid value for relfrozenxid in pg_class. Whereas AO/CO tables
carried valid relfrozenxid and were used for `datfrozenxid` calculation as well.

This commit makes sure only tables involved in `datfrozenxid` calculation,
actually carry valid relfrozenxid in pg_class and others don't. So, externally
someone executing age() function can easily ignore such tables by checking `not
relfrozenxid = 0`.

Fixes #2856.

When running pg_regress, sometimes you may want to exclude certain
tests from your schedule file from running. Before, you would have to
modify the schedule file to comment/ignore out the unwanted test. Now
we can do it from command line with --exclude-tests option that is
space and comma delimited.

Example:
./pg_regress --exclude-tests="test1 test2,test3 ... testN"

Authors: Abhijit Subramanya and Jimmy Yih

* Add ignore_checksum_failure GUC to reference

* Changes for review comments

* Promote embedded warning to a tagged warning

* Remove unnecessary "use" directives. Importing modules adds some overhead.

* Use File::Temp instead of POSIX.tmpnam for creating temporary files.
  File::Temp is used in atmsort.pm anyway, so also using it in explain.pm
  doesn't add extra overhead, like the otherwise-unused POSIX module does.
  The File::Temp API actually fits our needs better, so this shortens the
  code. And it allows removing the "use POSIX" directives, which again
  reduces the overhead of starting up the program.

* Use perl's built-in grep function, instead of launching the external
  grep program. Launching a new process is more expensive.

Altogether, these changes shave maybe 5-10 ms off the startup time of
gpdiff.pl, out of about 60 ms. That's not a huge difference, but every
little helps, and this is nice clean up in any case.

In PostgreSQL, we always just use 'diff', even on Solaris. Should be good
enough for GPDB too. (We don't officially even support Solaris anymore.)

The quote_string function will make sure that the value(if type is string) is
enclosed by `'`. This is introduced in previous commit(f936c4f3). We need
to make the change of gp_resource_manager meet the logic now.

Follow up commit for f936c4f3, which
added quotes around gpconfig values.
Signed-off-by: NMarbin Tan <mtan@pivotal.io>

There are better ways to set block size and table type, like with the
gp_default_storage_options GUC.

Signed-off-by: NLav Jain <ljain@pivotal.io>
Signed-off-by: NOleksandr Diachenko <odiachenko@pivotal.io>
Signed-off-by: NShivram Mani <smani@pivotal.io>
Signed-off-by: NJohn Gaskin <jgaskin@pivotal.io>
Signed-off-by: NAlexandra Wang <lewang@pivotal.io>

Signed-off-by: NNadeem Ghani <nghani@pivotal.io>

When you use gpconfig, users were forced to double quote the guc values.
For example:
    Prior:
       gpconfig -c pljava_classpath -v "'examples.jar'"

    Now:
       gpconfig -c pljava_classpath -v 'examples.jar' or gpconfig -c pljava_classpath -v examples.jar

Enhancement: Now all GUCs with vartype string will be wrapped in single
quotes before being written to the postgresql.conf.
Signed-off-by: NMarbin Tan <mtan@pivotal.io>

Now we support the resgroup memory_limit memory_shared_quota alteration
in below syntax:

	ALTER RESOURCE GROUP <group> SET MEMORY_SHARED_QUOTA <value>;
	ALTER RESOURCE GROUP <group> SET MEMORY_LIMIT <value>;

The new value may take effect immediately if the actual shared memory
usage is lower than the new value; otherwise it will delay the effect.
Signed-off-by: NHaisheng Yuan <hyuan@pivotal.io>

* resgroup: increase max slots for isolation tests.
* ICW: ignore resgroup related warnings.
* ICW: try to load resgroup variant of answers when resgroup enabled.
* ICW: provide resgroup variant of answers.
* ICW: check whether resqueue is enabled in UDF.
* ICR: substitude usrname in gpconfig output.
* ICR: explicitly set max_connections.
* isolation2: increase resgroup concurrency for max_concurrency tests.

We want to stop using gpfaultinjector utility in favor of using the
new gp_inject_fault extension. This commit creates the extension in
each test that requires it and replaces all uses of gpfaultinjector
utility with gp_inject_fault.

Authors: Abhijit Subramanya and Jimmy Yih

The MIRROREDLOCK macros in bufmgr.h referenced functions defined in
cdb/cdbfilerepprimary.h. Add an #include for that in bufmgr.h itself,
otherwise all the .c files that #include bufmgr.h and use those macros
need to include it.

Remove the now-unnecessary includes from .c files. This reduces our
diff footprint vs. upstream nicely.

The pattern of palloc'ing a Datum and isnull array is ubiquitous, no point
in hiding it behind a function, especially when the function only has one
caller.

When running gpconfig within the source code, you'll get the following:
$ ./gpMgmt/bin/gpconfig --help
  OptParser instance has no attribute 'helpStr'

fix this by initializing the help string list

These calls got lost during the 8.3 merge. There was a different mechanism
in GPDB earlier, to free these, and we replaced it with the upstream
mechanism in the merge, but missed these lines.

They were placed into wrong file.

This makes the code independent of the exact shape of pg_attribute. That
will save us some headaches when merging pg_attribute changes in the
future.

They were mostly marked as static in the prototype already, so this is just
for readability.

postgres.h is #included pretty much *everywhere*, so let's try to keep it
slim.

* SyncAgentMain function doesn't exist, so just remove its prototype.
* CdbProgramerrorHandler is only used in postgres.c, so make it static.
* Move gp_set_thread_sigmasks into miscadmin.h, where the prototypes for
  other functions in tcop/postgres.c are.

It compiles an old tag of gpdb for binary swap comparison testing
- It shouldn't go red
- It doesn't trigger on gpdb_src; often is just a stable cache

New jobs should also be added to the "All" group, but we expect that
there may be exceptions and it's not a dealbreaker

If the reusable anchors are declared at the end, some yaml parsers may
have trouble reading the file. In this case, pyyaml was throwing:

```
yaml.composer.ComposerError: found undefined alias 'ccp_create_params'
  in "<string>", line 702, column 11:
          <<: *ccp_create_params
              ^
```

We set CDB_PALLOC_TAGS regardless of USE_ASSERT_CHECKING on 81627e27. This bloated chunk header in release build, resulting in significantly more memory consumption in certain cases.

In this PR we are restoring the original behavior by setting CDB_PALLOC_TAGS only when USE_ASSERT_CHECKING is set. We are also removing unused code.
Signed-off-by: NFoyzur Rahman <foyzur@gmail.com>