No reason was specified for running those tests serially, tried and seem to run
fine in parallel. Also, dropped few drop tables from gpdtm_plpgsql test.

Just general freshening -- no major changes
Signed-off-by: NChumki Roy <croy@pivotal.io>

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Errlog files are not mirrored; the previous method for logging errors
(in a table) was removed
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>

Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>

Make consistent with:
https://github.com/greenplum-db/gpdb/commit/d7e6e0ecac5c49d16c68fcb827a23b0116d07b5aSigned-off-by: NChumki Roy <croy@pivotal.io>
Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>

Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>

* Renamed Storage for inet and cidr from plain to main
* Removed or change test usage of \d+ as it's very brittle/error prone.
Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>

The log errors into syntax no longer exists in master.

The enhanced_tables test makefile used the gcc from compilation instead of the system's gcc.

The answer files were updated to take into account the lack of error table.

This reverts commit fcdd8539.

This was breaking gpcloud S3 test.

GP Orca should generate a NOTICE when falling back to legacy planner for
external partition table.

This will correctly report the invalid argument instead of
the last one passed in this brings us up-to-date with upstream commit 86947e66.

There are a few postgres interface libraries such as psycopg which
hard code the type OID. If we don't use the same OID's as upstream
these interfaces will fail to recognize the returned values as json

The original patch could not use the upstream OID's as there was a
conflict with the OID 114, this has subsequently been removed.

The QuickLZ implementation is only available as a proprietary addon
to GPDB, remove the leftover documentation from when the code was
in the GPDB tree.

This patch was backported earlier already, but now that we cherry-picked
the binary-upgrade work from 9.0, we must also pick the related parts
of 3d21a0f300, that were not applicable earlier.

In the passing, also pick the "if (secure)" checks to EchoQuery and
UseNewLine from the upstream commit. I don't know why those were not
picked earlier.

A client to the QD should never send these special 'M' or 'T' messages,
but let's not trust the client.

Make sure to call destroyPQExpBuffer() on buffers before leaking
allocated resources, and document why some buffers must be kept
until the end of the functions to avoid NULL pointer derefs.

Per gripes in Coverity

When exchanging a partition for an external relation, the inheritance
information should not be propagated as external tables doesn't support
attribute inheritance. The oldrel still gets the previously inherited
attributes as local though.

External tables cannot inherit attributes when acting as a partition
member in a partititioned table. Attribute inheritance was cleaned up
in upstream commit 02e64181 which was
part of the 8.3 merge, and as an effect of this external tables were
dumped as inheriting the partition parent attributes. Fix by always
setting the attributes as local for external tables and make it even
more explicit by altering the attribute check in dumpExternal to only
consider dropped attributes. Apply the fix to both pg_dump and
cdb_dump_agent albeit a tad differently as pg_dump has abstracted the
logic for printing column names.

Report and debugging by Chris Hajas, Lawrence Hamel and Karen Huddleston

Centos 6 defaults nprocs as 1024 for users. Many times in CI seen failures as
cannot fork process, hence better to set reasonable limits (currently equivalent
to what's recommended by admin guide) while creating gpadmin user.

There is already a preset GUC for the PostgreSQL version number in
machine readable form: server_version_num, and human readable form:
server_version. This adds a Greenplum counterparts for these as
gp_server_version_num and gp_server_version.

Previously gporca translator was only pruning the non-visible system columns from
the table descriptor for non-partition `appendonly` tables or if the
paritition table is marked as `appendonly` at the root level.

If one of the leaf partitions in is marked as `appendonly` but the root
is not, the system columns still appears in the table descriptor.

This commit fixes the issue by checking if the root table has
`appendonly` paritions and pruning system columns if it has.

TINC discover would try to import the file instead of the class when
given something like this:
tinc.py discover -t tincrepo/mpp/gpdb/tests -s dispatch/queryfinish

The -t path is added to sys.path and the -s is imported. The -s needs
to be in dots for proper class importing.

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

docs: removing dita 'to-topic' chunking, which causes the subnav to collapse when the topic is selected (#1678)

doc: updating README to indicate that the full-easy-install version of DITA-OT is required.  Download links also provided (#1676)

When a pulse build is interrupted, fetching artifacts fails due to being
unavailable for a short bit. Retry so it fails more cleanly

Use slimmer docker image for pulse-cloud

* adding source for best practices doc

* removing pivotal copyright

* adding missing graphics files