Most of these test additions are inspired from Pivotal's internal
testing and needed to be added to the open source installcheck to
give the community more test coverage.

If a PathKey contains a constant member, it can be evaluated without
any entries in the target list, and can always be returned in
cdbpullup_findPathKeyExprInTargetList. This fixes the "Unexpected intarnal
error" you got with the included test query.

Closes issue #348, reported by liruto. Thanks for the report!

This check ensured that distributed transaction log does not have
missing page, and if it does, initialize to zero.  This was only
relevant in old Greeplum releases and is no longer required.

Closes #476.

Changing WorkfileQueryspace_ReleaseEntry assert to check querySpaceNestingLevel == 0 when we release the entry.

When DELETEing or UPDATEing an inherited table, some tables in the
inheritance tree might need an explicit Motion node to bring the targeted
tuples back to the segment where they reside, and some might not. The code
to build the plan handled that correctly, but this assertion incorrecly
assumed that it's all or nothing.

Remove the assertion, as it doesn't seem very useful in the first place.
The code that inserted the Motion nodes is just above the assertion, and
the assertion was basically just testing the same thing that the code
just did, and not some general invariant that should always hold.

Fixes issue #332

It is left-behind work of "5b2af3cf"

This fix contains two part
1. Backport 30bf4689 from upstream
2. Sync the implementation of fillPGconn() with postgresql which is simpler and more robust.

QD should not expect end-of-stream comes from QEs who is not members of
direct dispatch and should not report warning message.

More fallout from the equivalence classes merge.

It's easy to see that the code was broken, as it would always return 'true'
regardless of what happened in the for-loop.

Most places treated WindowInfo.partkey_operators as an array of equality
operators, except for this one call, which assumed it to be an array of
comparison operators (<).

Running the olap_window regression test revealed this. olap_window is
currently not enabled in the schedule, and we clearly need to fix that,
but I'll leave that for another commit.

Commit fc6aedc2 added autoconf checks for
those libraries, but the AC_CHECK_LIB macros have the side-effect of adding
-lDDBoost and -emcconnect to LIBS, which means that they will be linked in
all binaries. That's not what we want, they should only be linked into the
few binaries that actually use them.

This hopefully fixes the build failure seen on some platforms.

Anaconda is a python release and GPDB is supposed to be able to work with it.
Currently, GPDB only support python 2.7.

Neither ddboost nor emcconnect had proper library or heaer file
checks and were not present in the pg_config.h.

Make the list of options in --help line up a little better and set
proper detailed descriptions on all options. Also set output text
on all options during the ./configure operation.

We no longer support --with-java, --enable-email or --enable-nls
so remove from definitions. Rather than removing enable_nls comment
it out and make comment match whats in configure.in though.

Update S3 extention codes v2

compatible with s3.amazonaws.com and s3-us-east-1.amazonaws.com regions
catch any exceptions thrown by C++ functions
set min and max values of threadnum and chunksize

and will move development to GPDB source tree after this.

Commit 03201855 failed to update
the unit tests related to the validate_tablenames function, so this
commit alters the function slightly to make it more unit-testable
and makes the necessary unit test changes.

Previously, gpdbrestore had no check to determine whether a table to be
restored with the -T option existed in the dump, and the restore would
either fail during the ANALYZE step with an unclear message or would
succeed if --noanalyze was used. This commit adds a check to fail early
if a nonexistent table is passed to -T.

column compression tests perform bunch of alter type commands,
affecting other tests. Better to perform such opertions on dedicated database.

new conflixt appear:
/opt/gcc_infrastructure/bin/ld: warning: libxbsa64.so, needed by ../../../../src/bin/pg_dump/cdb/libgpbsa.so, not found (try using -rpath or -rpath-link)

This reverts commit b9d8b615.

gptransfer starts multiple threads in workerpool to transfer each source and destination
pair, to ensure the order specified by user, batch-size should be set to 1.

Partition table transfer uses dictionary as a map between source and destination pair,
which will not follow the order of insertion. Since gpdb uses python 2.6 and the
OrderedDict is only available from 2.7, so updated with a workaround using list.

Authors: Pengcheng Tang, Lawrence Hamel

When applying motion, a merge other than normal gather motion should
be added on the top node if it has sort list, this can make sure that
tuples are still in order after gathered to QD. Only checking if top
level parsetree has sort clauses may miss the implicit order constraint
in a view

The old value of rpath is an absolute path on build host, which is
not exist on target machine. Change it to relative path.
After this commit, LD_LIBRARY_PATH could be removed. Problem is that
we still have a lot of extra dependency for enterprise building, so
LD_LIBRARY_PATH is still kept.

This is first release and doesn't support write operation.
S3 has its own unittest with gtest

These tests have not been updated recently to accomadate the new
changes in gpdb, needed to fix it up and make sure gpfdist still works.

We need to make sure that fstream struct gets initialized or we may
pay the price of accidentally freeing a random address that's not
malloced.