This is first release and doesn't support write operation.
S3 has its own unittest with gtest

These tests have not been updated recently to accomadate the new
changes in gpdb, needed to fix it up and make sure gpfdist still works.

We need to make sure that fstream struct gets initialized or we may
pay the price of accidentally freeing a random address that's not
malloced.

This will make it so that we can build gpfdist with or without
OpenSSL when doing the configure.
* Print a message that SSL is not supported if built without OpenSSL

As gpfdist will now be part of the gpdb build by default, we may just
treat it as part of gpdb core.
* Integrate gpfdist configure file to the top level configure and
  changed necessary files to accomadate the changes.
* Modify travis.yml for gpfdist structural changes
* Update gpfdist.c to use GP_VERSION from pg_config.h

Fix warning issues from transform.c
* There were many prototype warnings that was being mentioned.
  Added a headerfile for missing prototype warnings, also included the
  structs into the headerfile.

Replace src/port/glob.c
* src/port/glob.c is dead code at the moment and can be safely replaced by
  the windows changes from gpfdist/port

Check for libyaml:
* disable transformations for gpfdist if not found.

schema name, and table name.

This commit fixes the quotation and escaption for the
whole backup and restore, and resolves related issues which
block us from supporting special chars.

List of remarkable changes:

Removed gpcrondump shell script.
Renamed gpcrondump.py to gpcrondump

Added -S option in gpdbrestore for schema level restore instead of using wildcard '*'.
Added few methods to parse and extract databases, schemas, tables, and others ddl from plain dump file
      to support special chars
Added some behave tests under gppylib/test/behave/mgmt_utils/

Fixed gpcrondump deleting user specified schema file
Fixed gpdbrestore not validating non existed tables correctly.
Fixed the pg_get_partition_def() and pg_get_partition_template_def() function to
      dump DDL statement properly with quotation and escaping.
Fixed ddboost restore and Post data restore not forming filter command correctly

Updated -x option in gpcrondump to not use comma separated specification.
Updated -T option in gpdbrestore to not use comma separated specification.
Updated the pre and post restore filter to parse special chars within schema and table names
Updated some unit tests, behave tests and the help docs

Authors: Pengcheng Tang, Chumki Roy

The jump table was missing some entries, and hence the code wouldn't have
worked correctly. Fortunately it was all dead code, as sendInitGpmonPkts()
only called itself, there were no other callers.

This fixes issue #256. Thanks to Craig Harris for the report!

The 1.622 updates in b3668c40 adds
a depedency on CHint without adding the required header file to
build without warnings/errors.

- This is a placeholder Concourse CI pipeline and task. See concourse.ci
  for details on the Concourse system.

1, In extreme cases where we are acquiring resource queue lock and
cannot find it in share memory, GPDB would raise PANIC, which is not
desirable;

2, Change one log level from LOG to DEBUG1, because that code path would
hit much frequently after previous resource queue commit;

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.