- 13 1月, 2018 40 次提交
-
-
由 Jamie McAtamney 提交于
We will not be supporting these utilities in GPDB 6. References to gpcrondump and gpdbrestore in the gpdb-doc directory have been left intact, as the documentation will be updated to refer to gpbackup and gprestore in a separate commit. Author: Jamie McAtamney <jmcatamney@pivotal.io>
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
Once this gos through in CI, will help to reduce one more job and there by elimintae one more VM expense.
-
由 Max Yang 提交于
* Fix tests associated filespace. * Update expected result of gpinitstandby with no standby_master directory. Author: Max Yang <myang@pivotal.io> Author: Xiaoran Wang <xiwang@pivotal.io>
-
由 Max Yang 提交于
Server side should exclude sub directory even parent directory wanted.
-
由 Heikki Linnakangas 提交于
We don't need the extra 'xid' arguments or the 'frozen' variants of heap_delete() and heap_update() anymore. They were used by persistent tables.
-
由 Heikki Linnakangas 提交于
gpcheckmirrorseg needs to be reimplemented, if we want to keep doing this kind of calidation.
-
由 Heikki Linnakangas 提交于
In GPDB, there used to be an extra column in the result set. That was removed as part of the walreplication work, so it now matches the upstream. But forgot to update these PQgetvalue() calls in pg_basebackup accordingly. Based on @macroyuyang's original patch and diagnosis.
-
由 Heikki Linnakangas 提交于
Not needed anymore.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
GpArray doesn't have a 'standby_datadir'. 'None' was passed here before the back and forth on removing the local standby_datadir variables and reverting that change.
-
由 Heikki Linnakangas 提交于
Since we have backported streaming replication from PostgreSQL 9.0, we need to use XLogIsNeeded() rather than XLogArchivingActive(), to determine if WAL-logging is needed. This explains the 'CS_switch' TINC test failure.
-
由 Heikki Linnakangas 提交于
-
由 Jimmy Yih 提交于
This should create a dump that will work between 6.0 versions but still needs ideas on how it would work for going to earlier versions like 5.x.
-
由 C.J. Jameson 提交于
Commit 155fa5a2ea cleaned up filespaces and switched the `gpinitstandby -F` flag to be for the standby data directory. But it inadvertently removed the logic which took the master's data directory as default. This should fix gpexpand tests. Author: C.J. Jameson <cjameson@pivotal.io> Author: Shoaib Lari <slari@pivotal.io>
-
由 Shoaib Lari 提交于
Prefer to keep the options immutable after flag parsing See https://github.com/greenplum-db/gpdb/pull/4274 which uses a local variable for the standby_datadir -- that proposed pattern is parallel to the original filespace code. Author: C.J. Jameson <cjameson@pivotal.io> Author: Shoaib Lari <slari@pivotal.io>
-
由 Max Yang 提交于
* Change test cases for gpinistandby -F parameter. * Fix get standby data directory by gp_segment_configuration instead of pg_filespace_entry * Fix gpinitstandby to follow old behavior if option -d not given Author: Xiaoran Wang <xiwang@pivotal.io> Author: Max Yang <myang@pivotal.io>
-
由 Max Yang 提交于
A timeline history file would be generated to track timeline change, and we copy the last wal file as wal file of current timeline. The split point in history file would take care of correct recovery. Author: Xiaoran Wang <xiwang@pivotal.io> Author: Max Yang <myang@pivotal.io>
-
由 Asim R P 提交于
Make sure that recovery.conf file does not exist after promotion. The file is renamed to recovery.done, like in upstream.
-
由 Jacob Champion 提交于
The previous patch failed, since we could not actually access the catalog without some more initialization. Pull as much initialization from the old Pass4 as possible -- some of it is likely not needed, but this seems to get things working for now.
-
由 Xin Zhang 提交于
Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Ashwin Agrawal 提交于
The failure was due to filespace removal. Fixed to use correct syntax. Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
If this works will remove all other pg_twophase make targets and jobs from CI. As to run one test creating the full VM, is not efficient.
-
由 Jamie McAtamney 提交于
The previous check in gptransfer for matching source and destination filespaces has been changed to a check for tablespaces, since filespaces no longer exist. Also, gptransfer tests related to filespaces and the corresponding files have been removed or altered accordingly. Author: Jamie McAtamney <jmcatamney@pivotal.io>
-
由 Heikki Linnakangas 提交于
Filespaces are no more.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
CREATE/DROP TABLESPACE are not transactional, and are not recovered entirely cleanly if a crash happens at the right moment. That's a known issue, inherited from PostgreSQL, and we'll live with it.
-
由 Heikki Linnakangas 提交于
I missed this one in the previous commit.
-
由 Heikki Linnakangas 提交于
CREATE TABLESPACE isn't transactional. Rolling it back doesn't work properly. This is a known limitation in PostgreSQL, we'll live with it.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
* Disable tests with crash_type=failover_to_primary or failover_to_mirror. They were tightly-coupled with file replication. I'm not sure if we should have something to replace them... * Disable tests with cluster_state=change_tracking or resync. These states don't exist anymore. I don't think we need a replacement for these.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
CTAS isn't any different from a regular CREATE TABLE, as far as two-phase commit is concerned. We don't need to test it separately.
-
由 Heikki Linnakangas 提交于
We had allowed it in GPDB, when we had all the fancy persistent table and filespace mechanisms to track the created-but-not-yet-committed tablespace creation. The upstream mechanism is more crude, and can't handle that gracefully. For example, if you abort the CREATE TABLESPACE transaction, the directory structure would be left behind. Or worse, when you DROP TABLESPACE, the underlying directory is deleted immediately, even if the transaction aborts. Hence, put back the upstream limitation. That's been acceptable for Postgres, and is surely acceptable for GPDB as well.
-
由 Heikki Linnakangas 提交于
Backport from PostgreSQL 9.0: commit db64a9d20eeb0d3a52b7fb520a88bc68b73b374b Author: Bruce Momjian <bruce@momjian.us> Date: Tue Jul 20 18:14:25 2010 +0000 Properly replay CREATE TABLESPACE during crash recovery by deleting directory/symlink before creation. Report from Tom Lane. Backpatch to 9.0.
-
由 Ashwin Agrawal 提交于
This change help `FtsTestConnection()` to correctly report segment state. `probeWalRepPublishUpdate()` updating fts_status if primary/mirror gets marked as down. Also, removed all other states and code setting the same as its not used for anything.
-
由 Heikki Linnakangas 提交于
This is a far cry from actually making the tests work, but let's see what the next error is after this is fixed.
-