- 30 3月, 2017 6 次提交
-
-
由 Jesse Zhang 提交于
Not to be confused with a TINC test with the same name. This test was brought into the main suite in b82c1e60 as an effort to increase visibility into all the tests that we cared about. We never had the bandwidth to look at the intent of this test though. There are a plethora of problem of the bugbuster version of `schema_topology`: 0. It has very unclear and mixed intent. For example, it depends on gphdfs (which nobody outside Pivotal can build) but it just tests that we are able to revoke privilege of that protocol. 0. It creates and switches databases 0. The vast number of cases in this test is duplicating coverage for tests elsewhere in `installcheck-good` and TINC. Burning this with fire.
-
由 Omer Arap 提交于
-
由 Jamie McAtamney 提交于
This commit splits up the single backup.feature file (where each scenario both dumps and restores data) into two files, dumps_only.feature which performs all necessary dumps and is run against a 4.3 database and restores_only.feature which performs the corresponding restores and is run against a 5 database. It also adds and/or modifies Behave steps to account for differences in functionality between 4.3 and 5. It uses the installed GPDB python version when running behave tests. This is necessary when running different versions of Greenplum with the same behave feature file. Authors: Karen Huddleston, Chris Hajas, Todd Sedano
-
由 Chris Hajas 提交于
gpdbrestore improperly filters out blocks that contain drop statements. BEGIN..END blocks from dumps should always be included in the restore.
-
由 Chuck Litzell 提交于
-
由 Chumki Roy 提交于
* Remove a previously deprecated utility * Remove mentions of gpsnap Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
- 29 3月, 2017 3 次提交
-
-
由 Heikki Linnakangas 提交于
Commit fae97ae7 accidentally removed the prototype for matrix_add(), even though it didn't remove the function itself. Put back the prototype, to silence compiler warning about missing prototype.
-
由 Daniel Gustafsson 提交于
These datafiles were no longer used by any test, remove since they will otherwise just linger in there.
-
由 Ashwin Agrawal 提交于
[ci skip]
-
- 28 3月, 2017 5 次提交
-
-
由 Daniel Gustafsson 提交于
Error tables were removed in 5.0 but the syntax for creating them on external tables in pg_dump was left in. Remove the offending INTO <relname> syntax to ensure restoring works in 5.0+. Apply to pg_dump and cdb_dump_agent.
-
由 Daniel Gustafsson 提交于
appendPQExpBuffer() is a variadic function which interprets the second parameter as a printf format string. Where we just append a static string, use appendPQExpBufferStr() instead which is much faster. Where a single char is added, use appendPQExpBufferChar().
-
由 Daniel Gustafsson 提交于
When merging upstream releases, or inventing new GPDB specific code, new object types may be required to be added to pg_upgrade. This documents the process on a broad level.
-
-- it is red in pipeline with a report of OoM, but that could actually be a symptom of a missing library. This reverts commit e4976920.
-
由 Marbin Tan 提交于
* Rewrite Kerberos test suite * Remove obsolete Kerberos test stuff from pipeline and TINC We now have a rewritten Kerberos test script in installcheck-world. * Update ICW kerberos test to run on concourse container This adds a whole new test script in src/test/regress, implemented in plain bash. It sets up temporary a KDC as part of the script, and doesn't therefore rely on a pre-existing Kerberos server, like the old MU_kerberos-smoke test job did. It does require MIT Kerberos server-side utilities to be installed, instead, but no server needs to be running, and no superuser privileges are required. This supersedes the MU_kerberos-smoke behave tests. The new rewritten bash script tests the same things: 1. You cannot connect to the server before running 'kinit' (to verify that the server doesn't just let anyone in, which could happen if the pg_hba.conf is misconfigured for the test, for example) 2. You can connect, after running 'kinit' 3. You can no longer connect, if the user account is expired The new test script is hooked up to the top-level installcheck-world target. There were also some Kerberos-related tests in TINC. Remove all that, too. They didn't seem interesting in the first place, looks like they were just copies of a few random other tests, intended to be run as a smoke test, after a connection had been authenticated with Kerberos, but there was nothing in there to actually set up the Kerberos environment in TINC. Other minor patches added: * Remove absolute path when calling kerberos utilities -- assume they are on path, so that they can be accessed from various installs -- add clarification message if sample kerberos utility is not found with 'which' * Specify empty load library for kerberos tools * Move kerberos test to its own script file -- this allows a failure to be recorded without exiting Make, and therefore the server can be turned off always * Add trap for stopping kerberos server in all cases * Use localhost for kerberos connection Signed-off-by: NMarbin Tan <mtan@pivotal.io> Signed-off-by: NChumki Roy <croy@pivotal.io> Signed-off-by: NLarry Hamel <lhamel@pivotal.io>
-
- 27 3月, 2017 6 次提交
-
-
由 Daniel Gustafsson 提交于
The tiny2 suite was a cut-down version of qp_derived_table with no new tests added. The stransaction suite was already covered by the ICW suites gpdtm_plpgsql and trasaction. Neither of these two suites were no longer connected to any test schedule.
-
由 Peifeng Qiu 提交于
Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Heikki Linnakangas 提交于
Now that external tables use resource owners to clean up on abort, we no longer need to ensure that ExecutorEnd gets called on failed portals. Remove PG_TRY-CATCH block in nodeAgg.c that's no longer needed. This demonstrates well why we should not call ExecutorEnd on abort; there might well have been more places that previously needed a PG_TRY-CATCH block like this, but didn't have one. See also discussion on this on the gpdb-dev mailing list: https://groups.google.com/a/greenplum.org/forum/#!topic/gpdb-dev/-BTKTbLuP1k Re-applying this since the blocker was removed by ca3f5520. Signed-off-by: NAdam Lee <ali@pivotal.io>
-
由 Adam Lee 提交于
The old cdbfast test suite had these, move to ICW. Signed-off-by: NAdam Lee <ali@pivotal.io> Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Adam Lee 提交于
Generate certificates for gpfdists then place them into master and segments' data directories. After this commit, specifying gpfdist's `--ssl` option with `$MASTER_DATA_DIRECTORY/gpfdists` could enable gpfdists protocol for gpdemo. Also update `lalshell` to remove unnecessary lines. Signed-off-by: NAdam Lee <ali@pivotal.io> Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Daniel Gustafsson 提交于
[ci skip]
-
- 26 3月, 2017 2 次提交
-
-
由 Daniel Gustafsson 提交于
In order for higher-level wrappers around pg_upgrade to know what pg_upgrade does, this adds a trivial file based queue which reports information on the operations performed. When started with -X, or --progress, pg_upgrade will write progress as a set of operations to a logfile. At intervals of either X number of operations, or Y number of seconds, the file will be released and a new created such that the released file can be consumed by a wrapper program. The files will be named <sequence>.inprogress until released when they are renamed to <sequence>.done. The sequence is gapless. Once the file is renamed to <sequence>.done, pg_upgrade will never touch it again and it can at that point be removed. The format of the progress file is a simple semicolon delimited line-based protocol: <timestamp>;<cluster>;<operation>;<message>; timestamp is the number of microseconds since epoch; cluster defines either "new", "old" or "none"; operation defines what actually did happen and message contains the user defined message per report. The timestamp is monotonically increasing for each operation such that reading files in order is less important, operations can still be individually sorted. This commit includes a small set of progress report operations, while not likely to be the final set it's enough to show how more can be added. Discussion: https://groups.google.com/a/greenplum.org/forum/#!topic/gpdb-dev/CVgK36oU5Oo
-
由 Daniel Gustafsson 提交于
Partitioned tables with external tables in the partition hierarchy cannot be upgraded since external partition management is prohibited in utility mode (the partitioning system catalogs are not replicated to the segments). Add a check for external partitions and abort the upgrade if found.
-
- 25 3月, 2017 10 次提交
-
-
由 Haozhou Wang 提交于
This test is a bug reproducer of gpfdist, move it from cdbfast to keep the coverage. Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Marbin Tan 提交于
* Add unit test for gpstart for better code coverage. * Initial stab into creating unit tests for gpstart Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Marbin Tan 提交于
* Initial stab into creating unit tests for gpstop Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Tom Meyer 提交于
Signed-off-by: NDavid Sharp <dsharp@pivotal.io>
-
由 David Sharp 提交于
Signed-off-by: NTom Meyer <tmeyer@pivotal.io>
-
由 Tom Meyer 提交于
usermod -a to append supplementary groups doesn't work on SLES. Signed-off-by: NDavid Sharp <dsharp@pivotal.io>
-
由 Jingyi Mei 提交于
Signed-off-by: NDavid Sharp <dsharp@pivotal.io>
-
由 David Sharp 提交于
Signed-off-by: NJingyi Mei <jmei@pivotal.io>
-
由 Tom Meyer 提交于
Signed-off-by: NJingyi Mei <jmei@pivotal.io> Signed-off-by: NDavid Sharp <dsharp@pivotal.io>
-
由 Dave Cramer 提交于
* In production pljava_classpath can only be set by super user or in postgresql.conf In order to allow developers to set it for testing we add a GUC called pljava_classpath_insecure. This can only be set in postgresql.conf or a super user When it is true, pljava_classpath can be set by a user. * make pljava_classpath_insecure visible in show all
-
- 24 3月, 2017 8 次提交
-
-
由 mkiyama 提交于
* GPDB DOCS - Add BINARY keyword to COPY command * Very minor edits [ci skip]
-
由 Chuck Litzell 提交于
-
由 Daniel Gustafsson 提交于
Since we have the documentation in the repo now, avoid linking to the web version since the link is bound to do stale quickly.
-
由 Marbin Tan 提交于
-
由 Marbin Tan 提交于
gpmigrator and gpmigrator_mirror are older utilities to help the upgrade from 4.2 -> 4.3. This is no longer necessary; we are removing all related gpmigrator calls and mentions. * Remove gpmigrator from travis * Remove upgrade test Signed-off-by: NChumki Roy <croy@pivotal.io>
-
由 Marbin Tan 提交于
-
由 Marbin Tan 提交于
Previously, -a -m from gpstart still resulted into a prompt due to a bug. This actually made it such that the changed line did not run properly -- probably hung on the prompt, since we don't validate if gpstart actually runs properly. 6edeefec fixed the gpstart prompt issue and caused this issue (actually running with master only) to finally show up, which made the later tests to fail for unabling queries to the database.. Ensure that we start fresh by doing a gpstart -a instead of just doing master only.
-
由 yanchaozhong 提交于
-