Add more AO/CO test coverage which covers a fixed bug from v4.1.0.0. Also,
add some cardinality and domain tests on bitmap indexes and scans. Most of
these test additions are modified/inspired from Pivotal's internal testing.

- Change the current vagrant to clone the GPDB inside and run it, to avoid confusion between host and guest environment.
- Change the VM size to 8GB and 4 cpus to better compile and test performance
- At the end of the vagrant the GPDB will up and running with gpdemo (3 seg and 3 mirrors)
- use `vagrant up gpdb` to build GPDB with GPORCA using option --enable-orca
- use `vagrant up gpdb_without_gporca` to build GPDB without GPORCA
Signed-off-by: NXin Zhang <xzhang@pivotal.io>

We do not need to link all of the gpfdist libraries to
the backend. Make sure that gpfdist is the only one who uses
libyaml, libevent, and libapr-1 for now.

While fetching the pg_class or pg_type tuple using index, perform sanity
check to make sure tuple intended to read, is the tuple index is
pointing too. This is just sanity check to make sure index is not broken
and not returning some incorrect tuple to contain the damage.

This commit makes sure while accessing gp_relation_node through its
index, sanity check is always performed to verify the tuple being
operated on is the intended tuple, else for any reason index is broken
and provide bad tuple fail the operation instead of causing damage.
For some scenarios like delete gp_relation_code tuple case it adds extra tuple
deform call which was not done earlier but doesn't seem heavy enough to
be performed on ddl operation.

Since we only test the higher level "wrappers" for gp_dump, pg_dump. We
can remove those tests. gpmgmt1: gpsys1 is a depercrated functionality.
python mpp8987.py tests unicode for loggers, special characters can deal
with this now, so we can remove it.

Conflicts:
	src/test/regress/bugbuster/expected/bkup_gp.out
	src/test/regress/bugbuster/expected/bkup_pg.out
	src/test/regress/bugbuster/expected/gpmgmt1.out
	src/test/regress/bugbuster/known_good_schedule
	src/test/regress/bugbuster/sql/gpmgmt1.sql

Authors: Marbin Tan & Chris Hajas

Backport from upstream with this commit:

    commit bc8036fc
    Author: Tom Lane <tgl@sss.pgh.pa.us>
    Date:   Fri May 11 17:57:14 2007 +0000

        Support arrays of composite types, including the rowtypes of regular tables
        and views (but not system catalogs, nor sequences or toast tables).  Get rid
        of the hardwired convention that a type's array type is named exactly "_type",
        instead using a new column pg_type.typarray to provide the linkage.  (It still
        will be named "_type", though, except in odd corner cases such as
        maximum-length type names.)

        Along the way, make tracking of owner and schema dependencies for types more
        uniform: a type directly created by the user has these dependencies, while a
        table rowtype or auto-generated array type does not have them, but depends on
        its parent object instead.

        David Fetter, Andrew Dunstan, Tom Lane

Signed-off-by: NGeorge Caragea <gcaragea@pivotal.io>

* Fix stat check for older behave test:
    Used to rely on gp_restore to do the stat update, but is now on
    python.
* Fix the tests to indiviudally check the statistics for each
partition table as the top level table does not gather statistics from its
subpartitions.
* Add specific gpdbrestore -T stat update check
* Add specific gpdbrestore -S stat update check

Add unit tests for generating the correct tables to restore.

Authors: Marbin Tan & Chris Hajas

When doing a restore of a specific table or a specific schema (-T or -S)
with a full backup, it will update all statistics for all AO/CO tables; it should
update only the specified table/schema.

Moved gp_update_ao_master_stats from the C side to the python code.
gpdbrestore -T and -S will now update AO/CO stats through the python code

Authors: Marbin Tan & Chris Hajas

file.

Authors: Marbin Tan, Chris Hajas and Pencheng Tang

This brings the code in convert_IN_to_join() back the way it is in the
upstream, making merging easier.

And some other cosmetic cleanup to match upstream better.

This makes merging easier.

catullus.pl is no longer used to generate pg_type.h, since commit 30c6ae3e.
Update the instructions accordinly. The description of how pg_proc.h works
was slightly out-of-date as well, updated that too.

When we use error log, if the master finds a badly formatted data row, it
increments the rejected row count and then sends the row to the segment so that
it can be stored in the error log file. On the segments, the row gets parsed
again and the segment increments the reject count again.  For reporting the
total number of rejected rows to the user we sum up the rejected row count from
the master and the segments. We need to ignore the count from the master
because it will be included in the reject count from the segments.

Also includes additional cleanup and typo fix of variable name by Heikki
Linnakangas.

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 on AO/CO tables.  This commit
mostly adds extra coverage for indexes and partition tables.

based on patch by Daniel Gustafsson

We only have a few extra types in GPDB, so it doesn't seem worth maintaining
the catullus mechanism for updating pg_type.h. When a new column is added
in the upstream, we'll just fix the GPDB-added lines manually. There are no
GPDB-added columns in pg_type.h, so we don't need the GPDB_COLUMN_DEFAULT
tricks we used in pg_proc.h.

Catullus.pl still needs type information to map the type names in
pg_proc_gp.sql to type OIDs. It used to get that information from the
pg_type.sql file, but I changed it to read the DATA lines in pg_type.h
directly.

Also revert unnecessary whitespace and comment changes against upstream, to
make merge easier.

remove_unused_initplans() didn't notice if there were references to a
subplan in the PRECEDING or FOLLOWING clause of a window function, because
plan/expression walkers didn't visit the PRECEDING/FOLLOWING clauses. Fix
the walkers.

We already had a test case for this in the regression suite, in
gp_optimizer, but instead of fixing the bug we had memorized the internal
ERROR message in the expected output. Oopsie.

The code to remove unnecessary InitPlans assumed that an InitPlan can only
return a single Param, which is wrong. Fix the code to handle multiple
Params.

Bug report and test case by CK Tan.

ExecCopySlotHeapTupleTo() is not used anywhere (anymore) so remove.