Just simple code change to avoid memory allocation, copy and deallocation for
vpinfo array while adding column to CO table.

This reverts commit dd2f326f.

Earlier tests only worked if was run with cluster having 2 segments, if
number of segemnts changed the output differed and hence will cause
test failure, which shouldn't be the case.

Tests ported from Pivotal's TINC test suite.

Incremental backup uses modcount to decide if AO/CO table needs to be
included for incremental backup. So, update or delete to AO/CO must
increment the modcount, this adds validation for the same to ICG instead
of having it in some other complicated test framework.

Yes, append-only tables are not actually append-only in modern version of
GPDB, hence the oxymoronic name.

These tests are ported from Pivotal's TINC test suite which has not been
open sourced - we are porting tests out of the suite instead.

These tests have been ported from TINC which is a test framework used inside
pivotal.

The length of the filename column was fixed to 256 characters. Filenames longer
than 256 characters would get truncated.

Users should use error log functionality for error handling in external tables
and during copy since it is more robust and reliable than the old error table
functionality.

Revert "Make relation size estimate use default in case ANALYZE statistics are not available instead of asking QEs. This saves cost of the ask from QEs and makes planning a bit faster. Since we do not expect good plans in absence of statistics, we might as well use default estimates relation size as well"

This reverts commit 063830e8 temporarily. This introduces new logging messages for some regression tests, for which the expected output needs to be changed accordingly. Reverting this to avoid build failures for now and will push a new patch with the updated tests

Make relation size estimate use default in case ANALYZE statistics are not available instead of asking QEs. This saves cost of the ask from QEs and makes planning a bit faster. Since we do not expect good plans in absence of statistics, we might as well use default estimates relation size as well

Improving CentOS Vagrant scripts to improve OS configuration and isntallation

Cleanup CentOS 6 reference

Adding changes to Vagrant guide on CentOS

Minor fixes for ulimit file and sudo for gpadmin

Removing "gpadmin" user creation as it causes problems with source code access rights

Making IP address configurable through the Vagrantfile

Fixing issue with "yum update" breaking VBox tools

Hence, it won't interfere with parallel executed tests.
The database creation overhead is less than 1 sec on a warm instance.

[#111625692]
Signed-off-by: NJacob Frank <jfrank@pivotal.io>

This change applies only to column oriented tables (CO).  It reads
block directory entries for only those columns that appear in project
list (e.g. select clause).

Closes #369

This commit represents an overhaul of the test suite relating to Veritas NetBackup
integration with the backup and restore utilities. It has the same goals and makes
similar changes to this suite that were made to the base backup and restore suite
in commit e8889fc5, and also focuses on removing
any scenarios that test functionality that isn't directly related to NetBackup and
is therefore sufficiently tested in the other suite, to improve the usability of
the suite and dramatically decrease total runtime (down from ~15 hours to ~5 hours
on Pivotal test machines).

This commit represents a major overhaul of the backup and restore test suite,
with the following main goals:
1) Cut down the time required to run the tests (previous runtime was ~3.5 hours
on Pivotal test machines, now it's down to around 1 hour 15 minutes).
2) Make each test scenario independent, so that the database state at the start
of a scenario does not depend on which scenarios were run before it and failures
in one scenario will not cause later scenarios to fail as a result.
3) Group commonly used steps, remove redundant scenarios and unnecessary steps
within scenarios, standardize common database and table names, and perform
similar cleanup, both to cut down on runtime and to improve readability and
comprehensibility of the suite.

This set of patches brings in RI operator selection fixes for generic types;
OR case handling in find_nonnullable_rels and some fixes to the recent
to_char() patch and some missing catalog entries for XML functions.

 Conflicts:
	doc/TODO
	doc/src/FAQ/TODO.html
	doc/src/sgml/config.sgml
	doc/src/sgml/docguide.sgml
	doc/src/sgml/ecpg.sgml
	doc/src/sgml/func.sgml
	doc/src/sgml/geqo.sgml
	doc/src/sgml/gin.sgml
	doc/src/sgml/installation.sgml
	doc/src/sgml/libpq.sgml
	doc/src/sgml/mvcc.sgml
	doc/src/sgml/plperl.sgml
	doc/src/sgml/runtime.sgml
	doc/src/sgml/sql.sgml
	src/backend/commands/tablecmds.c
	src/backend/executor/nodeResult.c
	src/backend/libpq/be-secure.c
	src/backend/optimizer/plan/initsplan.c
	src/backend/optimizer/plan/setrefs.c
	src/backend/postmaster/postmaster.c
	src/backend/utils/adt/formatting.c
	src/backend/utils/adt/numeric.c
	src/backend/utils/adt/xml.c
	src/backend/utils/misc/guc.c
	src/backend/utils/misc/postgresql.conf.sample
	src/backend/utils/misc/ps_status.c
	src/include/catalog/catversion.h
	src/include/catalog/pg_aggregate.h
	src/include/catalog/pg_proc.h
	src/include/postmaster/postmaster.h
	src/include/utils/builtins.h
	src/include/utils/xml.h
	src/interfaces/libpq/fe-secure.c
	src/test/regress/expected/create_aggregate.out
	src/test/regress/expected/timestamptz.out
	src/test/regress/sql/create_aggregate.sql

If an error is encountered while reading data from external tables,
FILEAM_HANDLE_ERROR sets pstate->cdbsreh->errmsg to edata->errmsg. It then
invokes FreeErrorData(). pstate->cdbsreh->errmsg is used to print out the error
message if segment reject limit is reached. This is incorrect since the memory
region it points to is no longer valid.

This patch fixes the issue by using pstrdup to copy the error message instead
of assigning the pointer.

This commit replaces a bad debug message with the real pexpect.pxssh
Exception messages.

Authors: Jimmy Yih and Phil Goodwin

We shouldn't error out if plpythonu already exists, it's required for
the test to run but it's not the thing we're testing here.

This merge contains a large update to the autovacuum code breaking it up
into a worker based process model. Since parts of the code had been cherry-
picked from later commits already, pulled in a set of upstream patches by
cherry-picking the complete commit since the code in them was partly in and
partly required to make the diff cleaner. Full commitmessages are copied in
below. There are no changes made to the autovacuum integration in GPDB in
this commit though, it remains turned off and marked as defunct.

The timestamp formatting changes were already merged since before, this
commit brings in lots of new testcases for the code though.

 Conflicts:
	doc/src/sgml/config.sgml
	doc/src/sgml/func.sgml
	doc/src/sgml/libpq.sgml
	doc/src/sgml/runtime.sgml
	src/backend/access/transam/varsup.c
	src/backend/bootstrap/bootstrap.c
	src/backend/commands/vacuum.c
	src/backend/libpq/be-secure.c
	src/backend/optimizer/README
	src/backend/optimizer/geqo/geqo_eval.c
	src/backend/optimizer/path/joinrels.c
	src/backend/optimizer/util/joininfo.c
	src/backend/postmaster/autovacuum.c
	src/backend/postmaster/pgstat.c
	src/backend/postmaster/postmaster.c
	src/backend/storage/ipc/ipci.c
	src/backend/storage/lmgr/proc.c
	src/backend/tcop/postgres.c
	src/backend/utils/adt/datetime.c
	src/backend/utils/adt/formatting.c
	src/backend/utils/adt/timestamp.c
	src/backend/utils/init/miscinit.c
	src/backend/utils/init/postinit.c
	src/backend/utils/misc/postgresql.conf.sample
	src/bin/initdb/initdb.c
	src/include/miscadmin.h
	src/include/postmaster/autovacuum.h
	src/include/postmaster/postmaster.h
	src/include/storage/lwlock.h
	src/include/storage/pmsignal.h
	src/include/storage/proc.h
	src/include/utils/datetime.h
	src/include/utils/timestamp.h
	src/interfaces/ecpg/pgtypeslib/dt.h
	src/interfaces/libpq/fe-secure.c
	src/test/regress/expected/timestamptz.out

  commit 8aaecaf8
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Fri Mar 23 20:56:39 2007 +0000

    We no longer need to palloc the VacuumStmt node; keeping it on the stack is
    simpler.

  commit 6287eb7a
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Fri Mar 23 21:23:13 2007 +0000

    Separate fetch of pg_autovacuum tuple into its own function.

  commit a0abe87f
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Fri Mar 23 21:45:17 2007 +0000

    Separate the code to start a new worker into its own function.  The code is
    exactly the same, modulo whitespace.

  commit e019bbc9
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Fri Mar 23 21:57:10 2007 +0000

    Set the node properly, per Tom.

  commit f1a596bd
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Tue Mar 27 20:36:03 2007 +0000

    Cosmetic changes: rename some struct fields, and move the fetching of pgstat
    table entries to a separate routine.  Don't pass the pgstat database entry to
    do_autovacuum; rather, have it fetch it by itself.

  commit 7d4c9a57
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Wed Mar 28 22:17:12 2007 +0000

    Add the "recheck" logic to autovacuum worker code.  The worker first builds
    its table list and then rechecks pgstat before vacuuming each table to
    verify that no one has vacuumed the table in the meantime.

    In the current autovacuum world this only means that a worker will not
    vacuum a table that a user has vacuumed manually after the worker started.
    When support for multiple autovacuum workers is introduced, this will reduce
    the probability of simultaneous workers on the same database doing redundant
    work.

  commit e2a186b0
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Mon Apr 16 18:30:04 2007 +0000

    Add a multi-worker capability to autovacuum.  This allows multiple worker
    processes to be running simultaneously.  Also, now autovacuum processes do not
    count towards the max_connections limit; they are counted separately from
    regular processes, and are limited by the new GUC variable
    autovacuum_max_workers.

    The launcher now has intelligence to launch workers on each database every
    autovacuum_naptime seconds, limited only on the max amount of worker slots
    available.

    Also, the global worker I/O utilization is limited by the vacuum cost-based
    delay feature.  Workers are "balanced" so that the total I/O consumption does
    not exceed the established limit.  This part of the patch was contributed by
    ITAGAKI Takahiro.

    Per discussion.

  commit a115bfe3
  Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
  Date:   Wed May 2 15:47:14 2007 +0000

    Fix failure to check for INVALID worker entry in the new autovacuum code, which
    could happen when a worker took to long to start and was thus "aborted" by the
    launcher.  Noticed by lionfish buildfarm member.

This reverts commit a19e0e7e. I had misread
the code, thinking that GP_HOSTADDRESS is a constant throughout the script.
It's not; it's set by the SET_VAR function, so the lookups were all looking
up different addresses. I did not notice that while testing on a single
host.

I still think the "sleep 2" is unnecessary, but I'm now afraid of touching
this because I don't have a multi-host setup at hand to test with. So revert
the whole commit .

Spotted by Jimmy Yih.