We don't do DROP LANGUAGE in the test (anymore. The bogus output is
ignored, but let's be tidy.

to/from client(second submission)

This is intended for scenarios where QD hangs sending data to client(
e.g, client is buggy not receiving data), or hangs waiting for data
from client(e.g, COPY foo FROM stdin);

There is a send mutex to prevent from sending a message to client when
another message is in the middle of sending, however, this send mutex
can lead to self deadlock in some cases, including this hanging send()
case; this commit also resolve this kind of self deadlock, at the cost of
discarding some message, which is acceptable when the process is dying.

Worker is the basic thread class used by gpdb utilities, if there are no commands in queue for Worker to consume, thread will be blocking for 5 seconds even though haltWork() is called. This fix send dummy command into queue so thread can detect shouldStop flag immediately.

failure fixed)

In some error cases, the resource queue lock is not released, hence
leading to lock leak and inconsistent resource queue status; this commit
overhauls the resource queue locking code to complete the cleanups if error
or signal happens during acquiring resource queue lock; meanwhile, some
unnecessary code blocks are removed and unreasonable code are fixed to make
it easier for reading and understanding;

With PostgreSQL, if you do "SELECT * FROM foo WHERE id = 1 and id = 2",
you get a Scan node on foo, with a gating Result node with False one-time
filter. That's what you also got on GPDB before this patch. Before merging
the equivalence classes patch, however, you got a Result node with
False one-time filter, with no subplan. This patch changes the behaviour
back to that.

Avoiding the planning saves some time during planning, as we don't need
to decide how to scan the relation. But more importantly, a stand-alone
Result node with no subplan can be executed on any segment, so the planner
can avoid unnecessary Motion nodes in some cases.

In the recent work to port tests from tinc to icg a duplicate entry
for this testsuite snuck in.

Closes #406.

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