Add support to the vagrantfiles for having additional synced_folders
locally without having to patch the Vagrantfile. Local folders are
configured in a YAML file in the same directory as the Vagrantfile
on the following format:

    synced_folder:
       - local: ../../../orca/gporca
         shared: /gporca
       - local: ../../../orca/gpos
         shared: /gpos

This also add comments to clarify the RTT computational logic

Need to check UDPIC_FLAGS_STOP flag when the ACK sequence equals to receivedAckSeq. Otherwise,
The receiver will keep polling ACK and the sender will keep sending ACK.

This reverts commit f3134604.

This reverts commit e929d4d0.

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.

The main change in this set of patches is that function expressions and
value lists are placed the FunctionScan and ValuesScan planner nodes. This
avoids having to look them up in the range tables during execution. Since
the executor now relies on this behavior the gpopt Orca libraries had to
be updated as part of this.

 Conflicts:
	doc/FAQ_DEV
	doc/TODO
	doc/src/FAQ/FAQ_DEV.html
	doc/src/FAQ/TODO.html
	doc/src/sgml/array.sgml
	doc/src/sgml/func.sgml
	doc/src/sgml/installation.sgml
	doc/src/sgml/libpq.sgml
	doc/src/sgml/mvcc.sgml
	doc/src/sgml/ref/pg_config-ref.sgml
	doc/src/sgml/spi.sgml
	doc/src/sgml/syntax.sgml
	src/backend/executor/execAmi.c
	src/backend/nodes/outfuncs.c
	src/backend/optimizer/path/allpaths.c
	src/backend/optimizer/path/clausesel.c
	src/backend/optimizer/plan/planner.c
	src/backend/optimizer/plan/setrefs.c
	src/backend/optimizer/plan/subselect.c
	src/backend/optimizer/prep/prepunion.c
	src/backend/optimizer/util/clauses.c
	src/backend/tcop/pquery.c
	src/backend/utils/adt/datetime.c
	src/backend/utils/adt/formatting.c
	src/bin/pg_dump/pg_backup_custom.c
	src/bin/pg_dump/pg_backup_tar.c
	src/bin/psql/describe.c
	src/include/catalog/catversion.h
	src/include/nodes/nodes.h
	src/include/nodes/primnodes.h
	src/include/nodes/relation.h
	src/include/optimizer/clauses.h
	src/include/optimizer/planner.h
	src/include/optimizer/subselect.h
	src/include/utils/datetime.h
	src/interfaces/ecpg/pgtypeslib/dt.h
	src/interfaces/ecpg/pgtypeslib/dt_common.c
	src/interfaces/libpq/fe-connect.c
	src/pl/plpgsql/src/gram.y
	src/tools/msvc/Solution.pm
	src/tools/msvc/genbki.pl

This reverts commit 8443c62e.

Authors: Jimmy Yih and Chris Hajas

I tried running this, and got a ton of errors. I don't think anyone's
used this for ages, so let's stop pretending that you might want to run
it. It might be a useful tool, as might some other style-checker or static
analysis tool, but this doesn't seem useful in its current state.

There is nothing special about these tables, views, or functions. We have
tons of objects like this all over the place. Let's just drop these.

The countrylist1 table was not used for anything either.

Makes it run a bit faster, I hope.

Now that some of the objects are created in 'regression' database, rather
than a newly created database, rename some objects to avoid clashing with
other bugbuster tests that use the same object names.

I wondered for a long time, why there are two copies of some DDL statements
in the .sql file, but only one copy in the .out file, and the test still
passes. Turns out that some of the DDL commands in the test file were inside
COPY data block. Instead of using valid-looking DDL as test data, put a
more explicit notice there. Perhaps putting a long block of valid queries
after a bogus "\.   " marker is a useful thing to test, but the point of the
test really should be explained explicitly.

heap_table_drop_col3 database is never created, so there's no point trying
to drop it. And no point in dropping objects in the db_test_bed database
in the beginning of the test: they won't exist, because we just created the
database.

Surely we have enough test coverage for creating a database with a regular,
lower-case name, or one with a number in it. We do both of those things
as part of initdb, for example.

Makes it nicer to run the test manually with pg_regress.

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.