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.

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>

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

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.

Moves the Python and Perl version tests in under ignore blocks to
make the test less fragile. Testing for specific versions is not
ideal, if this is to be kept as a real test it should be rewritten
to look for interpreters satisfying minimum version requirements
rather then exact (although the value of that can be argued as
well). Keep the version output in the test though since it can be
good information when debugging where access is limited to the
regression.diffs file. Also fix a trivial typo in a comment while
in there.

Commits backported from upstream are listed below.

	commit 87f2ad13
	Author: Tom Lane <tgl@sss.pgh.pa.us>
	Date:   Sun Mar 27 12:51:04 2011 -0400

	    Fix plpgsql to release SPI plans when a function or DO block is freed.

	    This fixes the gripe I made a few months ago about DO blocks getting
	    slower with repeated use.  At least, it fixes it for the case where
	    the DO block isn't aborted by an error.  We could try running
	    plpgsql_free_function_memory() even during error exit, but that seems
	    a bit scary since it makes a lot of presumptions about the data
	    structures being in good shape.  It's probably reasonable to assume
	    that repeated failures of DO blocks isn't a performance-critical case.

	commit 42b2907d
	Author: Tom Lane <tgl@sss.pgh.pa.us>
	Date:   Sun Nov 29 03:02:27 2009 +0000

	    Add support for anonymous code blocks (DO blocks) to PL/Perl.

	    Joshua Tolley, reviewed by Brendan Jurd and Tim Bunce

	commit 9048b731
	Author: Tom Lane <tgl@sss.pgh.pa.us>
	Date:   Tue Sep 22 23:43:43 2009 +0000

	    Implement the DO statement to support execution of PL code without having
	    to create a function for it.

	    Procedural languages now have an additional entry point, namely a function
	    to execute an inline code block.  This seemed a better design than trying
	    to hide the transient-ness of the code from the PL.  As of this patch, only
	    plpgsql has an inline handler, but probably people will soon write handlers
	    for the other standard PLs.

	    In passing, remove the long-dead LANCOMPILER option of CREATE LANGUAGE.

	    Petr Jelinek

Closes #449

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!

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

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.

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

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

master before dispatching the command to segments.

gp_truncate_error_log() function first dispatches the permissions check to the
segments and prints out the results before performing the check on the master.
This makes it hard to test this function if the cluster is configured with a
different number of segments than the test since different number of segments
produce different number of lines in the output. Performing the check first on
the master will cause the transaction to error out immediately and will be
easier to test.

segments configured in the cluster.

This reverts commit 8443c62e.