- 22 3月, 2018 4 次提交
-
-
由 Todd Sedano 提交于
[ci skip]
-
由 Ashwin Agrawal 提交于
To help debug the issue, PANIC incase encounter this shouldn't happen case.
-
由 Lisa Owen 提交于
-
由 Mel Kiyama 提交于
-
- 21 3月, 2018 9 次提交
-
-
由 Jim Doty 提交于
Update README based on feedback from a new developer to the GPDB codebase [ci skip] Co-authored-by: NJim Doty <jdoty@pivotal.io> Co-authored-by: NKevin Yeap <kyeap@pivotal.io>
-
由 David Sharp 提交于
-
由 David Sharp 提交于
-
由 Todd Sedano 提交于
Replaces lists of pip installs with a python requirements file Before pip install would use latest version of python libraries. Now we specify the library version found in the pythonsrc-ext repo. I used pipenv to find a set of version numbers that have consistent dependencies.
-
由 Nadeem Ghani 提交于
We have been using a very old version of paramiko, which is causing errors in gpssh-exkeys and gpseginstall on FIPS-enabled systems, in particular RHEL7.4. These errors are due to the ssh daemon not accepting deprecated cryptographic algorithms. Upgrading paramiko fixes these issues, but also introduces a new dependency on python-ecdsa. Additionally, this updates the pythonsrc-ext git submodule accordingly. Co-authored-by: NNadeem Ghani <nghani@pivotal.io> Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Co-authored-by: NJim Doty <jdoty@pivotal.io>
-
由 Mel Kiyama 提交于
* doc: analyzedb - add note about removing previous snapshots to recover space. * docs: analyzedb -add link to analyze command and analyzedb utility.
-
由 Todd Sedano 提交于
'brew install python' used to pull in python 2 Now is pulls in python 3 This commit explictly uses python 2
-
由 Ashwin Agrawal 提交于
This reverts commit 40b3b16c. Now that CI is bumped to concourse 3.9.2, lets see if we can live without this restriction.
-
由 Jesse Zhang 提交于
-
- 20 3月, 2018 15 次提交
-
-
由 Richard Guo 提交于
-
由 Richard Guo 提交于
By default the memory management in resource group is implemented by tracking every memory alloc/free in memory context. To support external components ( such as plcontainer) which do not use memory context, cgroup memory auditor is added into resource group. Note that catalog table pg_resgroup is changed.
-
由 Lisa Owen 提交于
-
由 Jimmy Yih 提交于
RawColumnDefault was removed previously as part of a commit that fixed pg_attrdef oid inconsistency between the master and primaries. This is not an issue anymore since we send pre-assigned oids during dispatch since Greenplum 5X and have checks around it in the code. We also have an oid_consistency test in src/test/regress that passes, and gpcheckcat doesn't complain. It seems like we're covered here. [ci skip]
-
由 Jimmy Yih 提交于
The FIXME comment asked whether or not we wanted to remove the check on CAC_WAITBACKUP. It is true that we do not currently use WAITBACKUP state, but we should continue to have the code. It will prevent some merge conflicts during postgres merge, and we may use it sometime in the future if applicable to any future Greenplum features. [ci skip]
-
由 Ben Christel 提交于
Authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Ben Christel 提交于
Authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Ben Christel 提交于
- The CMakeLists file is for CLion IDE code intelligence only. - We only look for sources in these directories because otherwise CLion might be confused by duplicated source files, e.g. for libpq Authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Ben Christel 提交于
This follows the pattern of other scripts like make_etags. Authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Amil Khanzada 提交于
Co-authored-by: NAmil Khanzada <akhanzada@pivotal.io> Co-authored-by: NDavid Sharp <dsharp@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Asim R P 提交于
- Use standard PMSignal mechanism to trigger FTS probes from dispatcher. - Use statusVersion flag only to indicate if a probe cycle resulted in configuration update. This was overloaded to also unblock callers waiting for FTS probe to be triggered and finished. - Use a separate flag "probeTick" for this purpose. Co-authored-by: NAshwin Agrawal <aagrawal@pivotal.io>
-
由 Ashwin Agrawal 提交于
While mirror is in grace period based on value of GUC `gp_fts_mark_mirror_down_grace_period`, it should not be marked down by FTS. So, adding coverage to validate the same. Plus modifying the test to use GUC to speed-up marking mirror down for intentional case.
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
Mirror is provided with grace period before being marked as down. FTS probes during this grace period interval, return retryRequested to probe request. Based on `retryRequested` should retry probes to primary and incase number of retries reach retry limit of `gp_fts_probe_retries` must skip marking such mirror down as still primary has not given go ahead to mark it down. Only when `retryRequested=false`, mirror must be marked down.
-
- 17 3月, 2018 2 次提交
-
-
由 Jimmy Yih 提交于
The fixme comment was placed here to warn that the implementation might be backwards on Greenplum 4.X and 5.X. The concern is not valid for Greenplum 4.X because there is no lazy xids. However, the concern is indeed valid for Greenplum 5.x. This is noted and will be changed on the 5X_STABLE branch. [ci skip]
-
由 Ekta Khanna 提交于
Prior to GPORCA version 2.55.10, ORCA produced a plan with Redistribute Motion on the hstore attribute(which is not a "GPDB hashable" type). This caused queries to fail with the error like: ERROR: Type 40963 is not hashable. This FIXME was added in `contrib/hstore/sql/hstore.sql` to run such failing queries with planner. Since the issue has been fixed in ORCA, removing it.
-
- 16 3月, 2018 10 次提交
-
-
由 Daniel Gustafsson 提交于
cache_test_acquire was incorrectly spelled in the test definition struct making it hard to run as a single test (without using the same typo).
-
由 Heikki Linnakangas 提交于
The code was quite confused on whether this was a switch-case or an if-else statement.. The command tag is unfortunately not included in pg_regress output, so this is not reflected in regression tests, even though we have ALTER EXTERNAL TABLE commands in the test suite. Fixes github issue #4377.
-
由 Heikki Linnakangas 提交于
This function was made unnecessary by commit b3f300b9, which changed GetOldestXmin() to "include" any distributed snapshots, too. rewriteheap.c no longer changes the freezeXid it's given, so there's no need for a function to get the new value back from it.
-
由 Heikki Linnakangas 提交于
We had removed these earlier, when we didn't have GIN indexes. Now we do.
-
由 Jimmy Yih 提交于
This argument was introduced when master/standby WAL replication was implemented to handle persistent table cases. Since persistent tables have been removed, we no longer need this argument to mdtruncate. This takes care of a GPDB_84_MERGE_FIXME.
-
由 Taylor Vesely 提交于
This reverts commit a21da89e. These changes are obsolete now that persistent tables have been removed. Co-authored-by: NAsim R P <apraveen@pivotal.io>
-
由 Jacob Champion 提交于
When upgrading to 8.4, upstream's pg_upgrade refuses to copy old sequence data due to a change in columns. However, that check also prevented copying of sequence data during an 8.2->8.3 upgrade -- Postgres doesn't care about this case, but GPDB does. Don't omit the copy if we're upgrading to 8.3, and enable the 8.2 heap upgrade for sequence tables so that the page makes sense in the new database.
-
由 Jacob Champion 提交于
Follow-up to 71916050. Checksums were backported to Postgres 8.3, so we ignore them for <= 8.2. While we're at it, switch the data_checksum_version from a false assignment to a zero assignment, to match upstream. The actual implementation is an unsigned int; Postgres master incorrectly uses a bool type in the declaration.
-
由 Jacob Champion 提交于
Follow-up to e8de956e. Correct the GPDB 5 check to use Postgres 8.3's version number, and correctly return the cached value from the GPDB 4 check.
-
由 Asim R P 提交于
This state was meant to prevent auxiliary processes from waiting from syncrep. As far as we can tell, auxiliary process should not be calling SyncRepWaitForLSN() unless it is committing a transaction. And if it is committing a transaction, it better wait for mirror to flush XLOG upto the commit LSN. One example of an auxiliary process committing a transaction is FTS, when it updates cluster configuration on master. Co-authored-by: NTaylor Vesely <tvesely@pivotal.io>
-