Removed one test that was checking for a memory leak by attempting to run the system out of memory.
Refactored one test that was checking for a large insert into a table with a bitmap index.

Closes #660.

[#116336737, #117671863]

Commit 9d19664c ported a test from cdbfast to master, which uses gp_fault_inject mechanism to throw a SIGSEGV.
We remove this test because i) gp_fault_inject works only if USE_TEST_UTILS = 1, while when we test GPDB, we set USE_TEST_UTILS to 0, and ii) throwing segmentation faults in ICG is a wrong approach.

Fixes compiler warning for implicit declaration due to missing
headerfile include:

  copy.c:4143:6: warning: implicit declaration of function
     'reconstructTupleValues' is invalid in C99
     [-Wimplicit-function-declaration]

Backport from upstream and related commits are

    commit e5fe2e84
    Author: Tom Lane <tgl@sss.pgh.pa.us>
    Date:   Fri Nov 9 23:58:32 2007 +0000

        Recognize RETURN QUERY via a textual test, so that QUERY doesn't need to be
        a plpgsql keyword.  This avoids springing a new reserved word on plpgsql
        programmers.
        For consistency, handle RETURN NEXT the same way.

    commit b2b9b4d5
    Author: Neil Conway <neilc@samurai.com>
    Date:   Wed Jul 25 04:19:09 2007 +0000

        Implement RETURN QUERY for PL/PgSQL. This provides some convenient syntax
        sugar for PL/PgSQL set-returning functions that want to return the result
        of evaluating a query; it should also be more efficient than repeated
        RETURN NEXT statements. Based on an earlier patch from Pavel Stehule.

Committers: Kuien Liu and Haozhou Wang

The tests were added in commit 7d0325e4
and were not properly translated from Pivotal's internal tests to the
pg_regress tests. They now properly test CREATE RULE on AO/CO tables.

Thanks to Heikki Linnakangas for catching this issue.

`set optimizer_join_arity_for_associativity_commutativity=7` will hint
at the optimizer to stop exploring join associativity and join
commutativity transformations when an n-ary join operator has more than
7 children during optimization, pruning quite a bit of the search space.

We really shouldn't get a sentinel node here but if we for some reason
do we need/should handle it by erroring out rather than propagating the
sentinel.

Reviewed by vraghavan@

Commit 41dfd82b moved gpcheckcat from bin/lib to bin/ and installed a
symlink to maintain backwards compatibility. However, installing and
copying the symlink in the source tree makes Git complain that it's
an untracked file. Rather than adding it to .gitignore we might as
well do this in the installation directory since that's where we want
to maintain backwards compatability anyways.

Cleaned up a few comments around the installation as well while in
there.

The cursor test for external table is non deterministic. The query errors out
either during DECLARE cursor or during FETCH. If the query errors out during
DECLARE and we perform a FETCH after the DECLARE an extra line of error is
produced in the output stating that the transaction has been aborted. In the
case where FETCH errors out this error is not produced in the output. This
commit adds a separate expected answer file to handle the two cases.

CodegenUtils.
This closes #648
Signed-off-by: NFoyzur Rahman <frahman@gmail.com>

In gpconfigurenewsegment, the class ConfExpSegCmd inherits from the class Command.
Command uses a variable of type ExecutionContext which was updated back in December
2011 to include passing the Command object itself to the execute(), interrupt(), and
cancel() ExecutionContext methods. The author of that patch did not update the
gpconfigurenewsegment.ConfExpSegCmd class which overrides those methods. It doesn't
make sense to even override them in the first place so they should just be removed.

Fixes commit f569c1d1.  The query used
in this test to identify missing attributes returned values for both the
primary and mirror segments, and has been modified to avoid doing so.
Also, if an attribute is deleted from every segment this is detected as
an error with the master, rather than an error with each segment, so the
test now only deletes one segment's attribute so it can test for master
and segment error messages.

Authors: Chris Hajas and Jamie McAtamney

- gpcheckcat should return a return code of 0 if schemas are found/dropped
- Backfilled tests for leaked schema logging
- Also cleaned up typo in Makefile

Gpcrondump generates prefix for each different dump file:

For global objects, dump file prefix is gp_global_1_1_*, returned
by method generate_global_prefix().
For statistics dump, file prefix is gp_statistics_1_1_*, returned
by method generate_stats_prefix()

remove scripts directory.
remove LICENSE file since it's the same as GPDB's.
remove dead codes and meaningless comments.
reorder header includings alphabetically.
add a missing unit test for find_replace().
rename testing sql files.
rename source files.
optimize compiling flags.

Currently, the error reporting for duplicate key value violation for unique
indexes does not contain useful information for users when debugging. This
commit backports two commits from PostgreSQL (shown below) and updates our
multikey tuplesort to use the same. Now the error will display the first
instance of a duplicate key violation.

Authors: Jimmy Yih and Abhijit Subramanya

commit b680ae4b
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Sat Aug 1 19:59:41 2009 +0000

    Improve unique-constraint-violation error messages to include the exact
    values being complained of.

    In passing, also remove the arbitrary length limitation in the similar
    error detail message for foreign key violations.

    Itagaki Takahiro

 Conflicts:
	contrib/citext/expected/citext.out
	contrib/citext/expected/citext_1.out
	src/backend/access/common/indextuple.c
	src/backend/access/index/genam.c
	src/backend/access/nbtree/nbtinsert.c
	src/backend/utils/adt/ri_triggers.c
	src/backend/utils/adt/ruleutils.c
	src/include/access/genam.h
	src/include/access/itup.h
	src/include/utils/builtins.h
	src/test/regress/expected/alter_table.out
	src/test/regress/expected/arrays.out
	src/test/regress/expected/create_index.out
	src/test/regress/expected/plpgsql.out
	src/test/regress/expected/transactions.out
	src/test/regress/expected/uuid.out
	src/test/regress/output/constraints.source
	src/test/regress/output/tablespace.source

commit 527f0ae3
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Sat Aug 1 20:59:17 2009 +0000

    Department of second thoughts: let's show the exact key during unique index
    build failures, too.  Refactor a bit more since that error message isn't
    spelled the same.

 Conflicts:
	src/backend/access/nbtree/nbtinsert.c
	src/backend/utils/sort/tuplesort.c
	src/test/regress/expected/alter_table.out
	src/test/regress/expected/create_index.out

Add behave test for gpcheckcat: catalog problems for conflicting db ownership will generate repair scripts that have timestamped names (to avoid overwriting)
- add behave steps for removing and also validating directories that are relative to the current working directory (allows * globbing)
- criteria for determining that repair file was not overwritten:  run gpcheckcat twice, and expect 1 and then 2 repair scripts.
- verify that stdout reports "owner" error
- change criteria for gpcheckcat ownership: relax the pg_type check so that both 4.3STABLE and master report an ownership error for pg_type.

This was causing issues on make check where the logger gets inherited
by other unittests and causes unexpected log outputs.

Authors: Marbin Tan & Stephen Wu

Updates unique index query to find column names by querying pg_attribute instead of string-parsing the index definition.  This allows us to support opclasses as well as special characters in the column name.

The maximal number of distributed by columns is 1600, gpdb should error out when
it exceeds the limitation. Another thing is gpdb should allocate enough memory to
hold those columns, otherwise it will cause memory overflow.

Three functions are available now:
- convert_from(bytea, name) returns text
- convert_to(text, name) returns bytea
- length(bytea, name) returns int

Related commits (partial codes are backported before OSS but not actived)

    commit a9742f12
    Author: Tom Lane <tgl@sss.pgh.pa.us>
    Date:   Wed Jan 9 23:43:54 2008 +0000

        Remove incorrect (and ill-advised anyway) pfree's in pg_convert_from and
        pg_convert_to.  Per bug #3866 from Andrew Gilligan.

    commit 02138357
    Author: Andrew Dunstan <andrew@dunslane.net>
    Date:   Mon Sep 24 01:29:30 2007 +0000

        Remove "convert 'blah' using conversion_name" facility, because if it
        produces text it is an encoding hole and if not it's incompatible
        with the spec, whatever the spec means (which we're not sure about anyway).

    commit 55613bf9
    Author: Andrew Dunstan <andrew@dunslane.net>
    Date:   Tue Sep 18 17:41:17 2007 +0000

        Close previously open holes for invalidly encoded data to enter the
        database via builtin functions, as recently discussed on -hackers.

        chr() now returns a character in the database encoding. For UTF8 encoded databases
        the argument is treated as a Unicode code point. For other multi-byte encodings
        the argument must designate a strict ascii character, or an error is raised,
        as is also the case if the argument is 0.

        ascii() is adjusted so that it remains the inverse of chr().

        The two argument form of convert() is gone, and the three argument form now
        takes a bytea first argument and returns a bytea. To cover this loss three new
        functions are introduced:
        . convert_from(bytea, name) returns text - converts the first argument from the
          named encoding to the database encoding
        . convert_to(text, name) returns bytea - converts the first argument from the
          database encoding to the named encoding
        . length(bytea, name) returns int - gives the length of the first argument in
          characters in the named encoding

    commit 75c6519f
    Author: Tatsuo Ishii <ishii@postgresql.org>
    Date:   Sun Mar 25 11:56:04 2007 +0000

        Add new encoding EUC_JIS_2004 and SHIFT_JIS_2004,
        along with new conversions among EUC_JIS_2004, SHIFT_JIS_2004 and UTF-8.
        catalog version has been bump up.

Committers: Kuien Liu and Haozhou Wang

more readable format.

Previously, gpcheckcat identified tables with missing attributes but
displayed them in various locations in the output in a
non-standardized format. This commit summarizes all the tables with missing
attributes in one section at the end of the output in the format
"[database].[schema].[table].[segment id]".

Authors: Chris Hajas and Jamie McAtamney

This commit fixes issues below:

extractContent() might forward NULL to marker.
ListBucket() fogets to delete keylist when errors happen.
contents in ListBucketResult are not cleared.
downloader is not destroyed in unit tests.
get_opt_s3() and truncate_options() in unit tests need to be freed.
xmlNodeGetContent() needs to be freed.
xml.ctxt->myDoc needs to be freed.
function for the XML library needs to be cleared.

Thanks to Kuien and Valgrind.

Signed-off-by: NNikos Armenatzoglou <nikos.armenatzoglou@gmail.com>

- print out all information about violated indexes in the logs
- changes unique index check to also return the list of violated
  segments in order to support this

- optimize query to find all unique indexes
- omit rows with null values when searching for violated indexes

- more accurate function names in GPObject
- remove duplication of query strings
- make file import for test subject independent of current working
  directory
- update test names to match casing convention

- additionally, minor refactoring in gpcheckcat and unique index check

- Before this we were adding issues to the report but not actually
  setting the checkStatus variable to False