- 03 4月, 2019 16 次提交
-
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit d67ecc3f)
-
由 David Krieger 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit e3457667)
-
由 David Krieger 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit a5130acb)
-
由 David Krieger 提交于
Now that the previous commits have placed these tests in CLI_TESTS, we can remove references to this symbol. (cherry picked from commit 8988618e)
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit f676d2cc)
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 37a09d64)
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 8bb12f08)
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. (cherry picked from commit e7b5f462)
-
由 David Krieger 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 642c4c8f)
-
由 Kalen Krempely 提交于
Tag existing tests with @demo_cluster and @concourse_cluster annotations. The @demo_cluster tag denotes the scenario can run locally. The @concourse_cluster tag denotes the scenario that requires a remote cluster. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 53aad9c3)
-
由 David Krieger 提交于
Templatize gpmovemirrors into a single concourse job to run both concourse_cluster and demo_cluster tags separate tasks. Co-Authored-By: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 0df65394)
-
由 Zhenghua Lyu 提交于
Each gpexpand test case need a new environment. Previous code uses pkill to make sure no postgres process remaining and then uses gpstop to double confirm. However, pkill to terminate cluster may over-kill some other postgres process on the hosts. What's more, the interface `Given a working directory of the test as '/data/gpdata/gpexpand'` will remove the directory which also remove the $MASTER_DATA_DIRECTORY, so the following `gpstop` is useless because $MASTER_DATA_DIRECTORY is gone. Also, this introduce race conditon. This commit removes pkill and use gpstop interface to build a clean environment for each test case. Also it makes sure that `gpstop` is invoked at the very beginning of each test case.
-
由 Paul Guo 提交于
We've seen frequent pg_rewind test failures due to promotion timeout. We should increase the timeout. Also, add code to error out on timeout. Co-authored-by: NNing Yu <nyu@pivotal.io> Reviewed-by: Ashwin Agrawal
-
由 Paul Guo 提交于
Previously the default value is 0, so normally log rotation happens each day by default according to the other log related guc configurations. That often makes a single log file rather large in real users' environment. Limiting the log file size so that people could easiler open and search the log files.
-
由 Paul Guo 提交于
1) pm_launch_walreceiver was introduced in b824fe8f to avoid a potential deadlock when cluster is down after updating the new role in gp_segment_configuration but before sending promote signal. It is buggy now since some changes. We need to put pm_launch_walreceiver in shared memory since it's used in different processes. 2) The following assertion is not always true in a real scenario if the segment is being promoted. We could simply stop the connection for the !am_mirror case. ProcessStartupPacket() if (am_ftshandler) { Assert(am_mirror); Ning Yu and we had some discussions for these bugs. He contributed for issue 1 also. Co-authored-by: NHaozhou Wang <hawang@pivotal.io>
-
- 02 4月, 2019 5 次提交
-
-
由 Bradford D. Boyle 提交于
Related PR discussion: kmacoskey: Another piece of this can be removed with the same intention as the other removal. This line in the Makefile is related to a kfw snowflake dependency that was being vendored into the Clients/Loaders package as brought in by Ivy. Note the path, ext. It was dropped from Ivy by releng awhile ago, 2c6f4c9d#diff-271f398f0c07147024e7980737cddb7d . The cp here probably should have been removed along with the change to Ivy, but it was missed. It can be removed - but lets make sure the Clients team is aware. pf-qiu: I think it's safe to do this now. (cherry-picked from 22646c10) Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Sambitesh Dash 提交于
(cherry-picked from c0f49617) Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Sambitesh Dash 提交于
Since we have removed the Ivy dependency manager entirely from GPDB 6+, we do not need this code anymore. It used to copy Ivy-managed libraries into the Greenplum installation for packaging. (cherry-picked from 1cc3dfc8) Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Amil Khanzada 提交于
* Remove unused IVYREPO_ variables for CentOS 6/7 Ivy is no longer used for CentOS 6/7. Authored-by: NAmil Khanzada <akhanzada@pivotal.io> * Remove unused IVYREPO_ variables for Coverity Ivy is no longer used for CentOS 6/7 and will go away. The coverity pipeline is also puased at this point in time, but we'll clean this up now. (cherry-picked from c4c99bb0) Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io> Co-authored-by: NAmil Khanzada <akhanzada@pivotal.io>
-
由 Alexandra Wang 提交于
INSERT needs to Lock the child table on QD, otherwise the following dead lock scenario may happen if INSERT runs concurrently with VACUUM drop phase on an AppendOnly partitioned table. 1. VACUUM on QD: acquired AccessExclusiveLock on the child table 2. INSERT on QE: acquired RowExclusiveLock on the child table 3. VACUUM on QE: waiting for AccessExclusiveLock on the child table 4. INSERT on QD: waiting for AccessShareLock at ExecutorEnd() on the child table, this is after QE sends back which child it inserted Note that in step 2, INSERT only locks the child table on QE, it does not lock the child table on QD in the previous code. This patch adds the lock on QD as well to prevent the above dead lock. Added `insert_while_vacuum_drop` and updated `partition_locking` to reflect the changes (cherry-picked from c7fce844)
-
- 29 3月, 2019 2 次提交
-
-
由 Chuck Litzell 提交于
-
由 Chris Hajas 提交于
For ORCA commit "Fix crash when merging group containing CTE consumer" Authored-by: NChris Hajas <chajas@pivotal.io>
-
- 28 3月, 2019 5 次提交
-
-
由 Chuck Litzell 提交于
-
由 David Yozie 提交于
-
由 Zhenghua Lyu 提交于
BuildPartitionNodeFromRoot will always use root relid no matter what parameter is passed to it. There is an optimization we might do: for some cases, like if user directly insert into a child partition, then set estate->es_result_partitions to NULL to avoid dispatch it since a huge partition table's partition info may cost much memory. We can spike this later.
-
由 Bhuvnesh Chaudhary 提交于
-
由 Francisco Guerrero 提交于
* Fix bin_gpdb_centos6_icw_green versioned_file to store artifacts in gpdb_branch_6X_STABLE * Generate pipeline
-
- 27 3月, 2019 2 次提交
-
-
由 Jimmy Yih 提交于
Greenplum does not support this. These were originally removed in the postgres 8.3 merge iteration but the 8.4 through 9.4 merge iterations brought them back accidentally. This commit is going directly to 6X_STABLE because the postgres 9.5 merge iteration will remove the *.po translator files for master.
-
由 Wang Hao 提交于
For GP 6 beta, the release engineering team is removing the apr-util package from the list of bundled dependencies. Users will be asked to provide their own apr-util package, which can differ in the version on each platform. So it is necessary to verify gpperfmon is workable with the platform provided apr-util on each supported platform. Originally, gpperfmon test is done in CLI test suite, only covers centos6. This commit changed it to a dedicated suite in order to test multiple platforms. Note: on SLES12 does not need to install libapr-util1 to run gpmmon
-
- 26 3月, 2019 4 次提交
-
-
由 Lisa Owen 提交于
* docs - gpexpand.status_detail external_writable field * gpexpand.status tbl - updated col now timestamp without tz
-
由 Lisa Owen 提交于
* docs - organize contrib modules in ref guide * provides * insignificant edit
-
由 Chuck Litzell 提交于
* ALTER TABLE. Edits and fix example. * ALTER TYPE. Add IF NOT EXISTS and edits * ALTER VIEW. edits and add examples * clusterdb. small edit * CREATE EXTENSION. Edits mostly applied earlier. * CREATE FUNCTION. Compatibility edit. * CREATE RULE. Edits * EXPLAIN. small edits. * DROP RULE. minor edits * GRANT. revise server USAGE privilege description. * pg_restore. lots of edits. doesn't read PGDATABASE envvar. * REASSIGN OWNED. edits. Remove qualification that it doesn't change the database ownership * REASSIGN OWNED. edits. Remove qualification that it doesn't change the database ownership * Remove extraneous char * Changes from review
-
由 dyozie 提交于
-
- 25 3月, 2019 3 次提交
-
-
由 Jamie McAtamney 提交于
We add gpmovemirrors tests and add them to the pipeline as well. Using behave tags, some of the tests can run locally on a demo cluster. We also introduce Behave tag logic to choose which tests to run. <Co-Authored-By> Kalen Krempely <kkrempely@pivotal.io> <Co-Authored-By> Mark Sliva <msliva@pivotal.io> (cherry-picked from fdf8b611)
-
由 Taylor Vesely 提交于
This seems to have broken when we updated gprecoverseg to work with WAL rep. (cherry-picked from e9388cdb)
-
由 Mark Sliva 提交于
We removed the registerMirrorsInCatalog method from the cluster-wide utilities. Co-authored-by: NShoaib Lari <slari@pivotal.io> (cherry-picked from db9f0b14)
-
- 23 3月, 2019 2 次提交
-
-
由 Jacob Champion 提交于
Because set_next_rotation_time() was being called once per call to logfile_rotate(), the timestamp used to create the log file name was being advanced multiple times per rotation. This led to the creation of empty log files on disk that looked like they were from "the future". This code badly needs to be refactored -- the initial intent, for the text and csv implementations to be independent, is no longer the case -- but for now, we can hack around this problem by pulling the call to set_next_rotation_time() up one level. This will only be called if *all* logfiles are correctly rotated, to match the upstream logic (on failure, we loop around to the beginning and try to open all log files again). Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> (cherry picked from commit fc53bbf8)
-
由 Jacob Champion 提交于
Log rotations were happening well after the timestamp on the log file (e.g. a per-minute rotation might actually take place thirty seconds after it was supposed to). After the 9.2 merge, we were incorrectly shadowing the `now` variable, so the rotation delay only got bigger and bigger. Periodic logging (such as from FTS) caused us to break out of the wait by luck, but otherwise the syslogger would take longer and longer to wake up to perform a rotation. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> (cherry picked from commit 14a794e8)
-
- 22 3月, 2019 1 次提交
-
-
由 Ning Yu 提交于
These files used to be installed to ${prefix}/bin/ directory, but as they are not user documents we should not install them. Reviewed-by: NBradford D. Boyle <bboyle@pivotal.io> Reviewed-by: NBob Bao <bbao@pivotal.io> (cherry picked from commit b176c4e6)
-