Set the correct Wiki URL to use for the project, we have moved over
to using the Github wiki on the main repo and not the wiki on the
website repo.

Remove references to Pivotal Greenplum documentation in the README
and stick to greenplum.orc/docs/ there as those are the applicable
docs.  While there update the README.md to actually match reality,
the docs are now in the main repo.

utils/resgroup/resgroup.c.

Signed-off-by Richard Guo <riguo@pivotal.io>
Signed-off-by Gang Xiong <gxiong@pivotal.io>

database.

Signed-off-by Richard Guo <riguo@pivotal.io>
Signed-off-by Gang Xiong <gxiong@pivotal.io>

Works include:
* define structures used by resource group in shared memory;
* insert/remove shared memory object when Create/Drop Resource Group;
* clean up and restore when Create/Drop Resource Group fails;
* implement concurrency slot acquire/release functionality;
* sleep when concurrency slot is not available, and wake up others when
releasing a concurrency slot if necessary;
* handle signals in resource group properly;

Signed-off-by Richard Guo <riguo@pivotal.io>
Signed-off-by Gang Xiong <gxiong@pivotal.io>

and resource group when 'resource_scheduler' is on, we need to change the
condition of the resource queue branches. Also, tidy up error messages related
to resource manager under these different GUC settings.

Signed-off-by Richard Guo <riguo@pivotal.io>
Signed-off-by Gang Xiong <gxiong@pivotal.io>

To fix the credential leak, make these jobs able to be public after
their job history are scrubbed.

Also remove unnecessary -B, which benefits from 08ec642dSigned-off-by: NYuan Zhao <yuzhao@pivotal.io>

Signed-off-by: NDivya Bhargov <dbhargov@pivotal.io>

* Clean up from the removal of the client submodule (#2166)

* Clean up from the removal of the client submodule

* Cleanup

  - Update makefile to remove references to connectors
  - removed EULA header

added godb_packaging back into repo

deleted clients to match

* reapplied makefile changes after merge

* Clean up from the removal of the client submodule

* Cleanup

  - Update makefile to remove references to connectors
  - removed EULA header

Signed-off-by: NChris Hajas <chajas@pivotal.io>

Before when gprestore_filter failed, the restore command would claim
success

Sets pipefail for gp_restore filter invocation
Signed-off-by: NChris Hajas <chajas@pivotal.io>

* Rewrite syslogger unittest to not mock fopen()

Mocking fopen() caused an error in the pipeline due to an OpenSSL
init function segfaulting on the mock. Rewrite the test to only
test the interesting bit of open_alert_log_file() once the mocks
are taken away.

* Fix typo

Authors: Karen Huddleston and Vaibhav Tandon 

[ci skip]

* Removing DCA v1 reference; small edit for clarity [ci skip]

* line edit

* more line edits

* more edits

[ci skip]

* GPDB DOCS - add/update warnings

[ci skip]

* GPDB DOCS - add/update warnings - conditionalized Pivotal information.

[ci skip]

The behave step assumed OID and relfilenode are equal. This was changed
in commit 1fd11387.

Revert the patch since it broke tests for gprestore and gptransfer in
the main pipeline. While the test quoted in the original Jira passes
there seems to be more to it than meets the Jira.. Revert for now.
Reverts:

  commit 1bb0b765
  Author: Daniel Gustafsson <dgustafsson@pivotal.io>
  Date:   Wed Apr 5 13:07:10 2017 +0200

    Use backend quoting functions instead of libpq

    libpq is front-end code and shouldn't be used in backend processes.
    The requirement here is to correctly quote the relation name in
    partitioning such that pg_dump/gp_dump can create working DDL for
    the partition hierarchy. For this purpose, quote_literal_internal()
    does the same thing as PQescapeString(). The following relation
    definitions were hitting the previous bug fixed by applying proper
    quoting:

libpq is front-end code and shouldn't be used in backend processes.
The requirement here is to correctly quote the relation name in
partitioning such that pg_dump/gp_dump can create working DDL for
the partition hierarchy. For this purpose, quote_literal_internal()
does the same thing as PQescapeString(). The following relation
definitions were hitting the previous bug fixed by applying proper
quoting:

CREATE TABLE part_test (id int, id2 int)
  PARTITION BY LIST (id2) (
    PARTITION "A1" VALUES (1)
  );

CREATE TABLE sales (trans_id int, date date)
  DISTRIBUTED BY (trans_id)
  PARTITION BY RANGE (date) (
    START (date '2008-01-01') INCLUSIVE
    END (date '2009-01-01') EXCLUSIVE
    EVERY (INTERVAL '1 month')
  );

ALTER TABLE sales
  SPLIT PARTITION FOR ('2008-01-01')
  AT ('2008-01-16')
  INTO (PARTITION jan081to15, PARTITION jan0816to31);
ALTER TABLE sales
  ADD DEFAULT PARTITION other;
ALTER TABLE sales
  SPLIT DEFAULT PARTITION
  START ('2009-01-01') INCLUSIVE
  END ('2009-02-01') EXCLUSIVE
  INTO (PARTITION jan09, PARTITION other);

The previous cleanup of perforce integration from the makefiles
inadvertently left one reference to p4client/p4 in the releng
tools.mk. Remove by partially backport a fix for PostGIS gppkg
from the 4.3 tree.

Commit f41552e9 removed the upgrade code from gpstart, but took
some of the code to test connections with it. Reinstate the url
test but with self.dburl instead since it's the only remaining
value to test here.

Avoid python dependent output by using terse verbosity to make the
test suite more stable across environments.

Commit eb1740c6 added plpython_types to the REGRESS set as part
of a backport, the test suite was however not added until 9.2 in
upstream which is further up than our version. Remove until we have
caught up with 9.2.

Commit 644b2a9d synchronized our pl/perl with upstream and
tidied up the Makefile. Add the missing init_file which that
commit references for pg_regress.

The ./configure for the ICW run in Concourse needs to have the same
set of configure options as the compile job since it uses the config
status to determine which tests to run.

The fix is to perform the same steps as a TRUNCATE command - set new relfiles
and drop existing ones for parent AO table as well as all its auxiliary tables.

This fixes issue #913.  Thank you, Tao-Ma for reporting the issue and proposing
a fix as PR #960.  This commit implements Tao-Ma's idea but implementation
differs from the original proposal.

This is useful if a test wants to use gp_toolkit.__gp_{aoseg|aocsseg}*
functions.

Signed-off-by: NTom Meyer <tmeyer@pivotal.io>

Analyze collects a sample from the table, in case the
sample contains columns with huge length, it may
result in memory usage to go high cancelling the query.

This commit masks wide values `i.e pg_column_size(col) > WIDTH_THRESHOLD
(1024)` in variable length columns to avoid high
memory usage while collecting sample. Column values exceeding
WIDTH_THRESHOLD will be marked as NULL and will be ignored from the collected
samples tuples while computing stats on the relation.

In case of expression/predicate indexes on the relation, the wide columns will be
treated as NULL and will not be filtered out. Is it rare to have such
indexes on very wide columns, so the effects on stats (nullfrac etc) will be minimal.
Signed-off-by: NOmer Arap <oarap@pivotal.io>

The breakin/out functions should be marked as STRICT,
because the underlying C functions, textin/textout,
don't expect a NULL to be passed to them.
Signed-off-by: NEkta Khanna <ekhanna@pivotal.io>

Signed-off-by: NJim Doty <jdoty@pivotal.io>

A lot of tests assumed OID == relfilenode. We updated the tests to not assume
that anymore.

A lot of tests assumed OID == relfilenode. We updated the tests to not assume
that anymore.

These tests assumed OID == relfilenode. We updated the tests to not assume it
anymore.

A query in gpcheckmirrorseg.pl would lookup relfilenodes obtained from
physically diffing segment files between primaries and mirrors. The
issue with the query was that it only looked at master's catalog which
would most likely not contain the relfilenodes of the QE
segments, especially after introducing the relfilenode counter change. We union
all the QE segment catalogs with master's catalog and check by content id to
correct the query.

This is needed to prevent relations possibly overwriting each
other. The O_EXCL is present in postgres's mdcreate() but for some
reason we don't have it here. This adds it back.
Signed-off-by: NXin Zhang <xzhang@pivotal.io>

The master allocates an OID and provides it to segments during
dispatch. The segments then check if they can use this OID as its
relfilenode. If a segment cannot use the preassigned OID as the
relation's relfilenode, it will generate a new relfilenode value via
nextOid counter. This can result in a race condition between the
generation of the new OID and the segment file being created on disk
after being added to persistent tables. To combat this race condition,
we have a small OID cache... but we have found in testing that it was
not enough to prevent the issue.

To fully solve the issue, we decouple OID and relfilenode on both QD and QE
segments by introducing a nextRelfilenode counter which is similar to
the nextOid counter. The QD segment will generate the OIDs and its own
relfilenodes. The QE segments only use the preassigned OIDs from the QD
dispatch and generate a relfilenode value from their own nextRelfilenode
counter.

Current sequence generation is always done on QD sequence server, and
assumes the OID is always same as relfilenode when handling sequence client
requests from QE segments. It is hard to change this assumption so we have a
special OID/relfilenode sync for sequence relations for GP_ROLE_DISPATCH and
GP_ROLE_UTILITY.

Reference gpdb-dev thread:
https://groups.google.com/a/greenplum.org/forum/#!topic/gpdb-dev/lv6Sb4I6iSISigned-off-by: NXin Zhang <xzhang@pivotal.io>