- 06 4月, 2019 1 次提交
-
-
由 Adam Berlin 提交于
User defined functions cache their plan, therefore if we modify the plan during execution, we risk having invalid data during the next execution of the cached plan. ExecuteTruncate modifies the plan's relations when declaring partitions that need truncation. Instead, we copy the list of relations that need truncation and add the partition relations to the copy. (cherry picked from commit e3cf4f26)
-
- 05 4月, 2019 10 次提交
-
-
由 Daniel Gustafsson 提交于
Commit ea9df812 relaxes the requirement that all LWLocks are in a single array, which broke the LOCK_DEBUG code for trying to acquiring an LWLock. This is a meatball surgery attempt at making it at least compile and run, without trying to reinvent the old usecase. Minor tweaking of the code is also done to make LOCK_DEBUG cases be identified identically. Backported from master 3a1ced8f Reported-by: Simon Gao in Github issue #7251 Reviewed-by: Ashwin Agrawal
-
由 Lav Jain 提交于
-
由 Lav Jain 提交于
* Create a public dockerfile for compiling gpdb on ubuntu * Create directory /usr/local/greenplum-db-devel for installing greenplum * Move current ubuntu files to ubuntu16_ppa. Update readme
-
由 Chuck Litzell 提交于
* docs - remove ALTER SYSTEM reference * Restore source for ALTER SYSTEM ref, but leave out of maps. * Add ALTER SYSTEM to list of unsupported PostgreSQL features
-
由 Chuck Litzell 提交于
* Docs - removes replication port references Also replaces gpstate -p command output with more recent version * add missing line break to example
-
由 Daniel Gustafsson 提交于
Commit 99360f54 extended the offset numbers in the GIN posting list to 16 bits over upstream who use 11 bits. This however means that the assertion around ip_posid is no longer valid as it's always true, causing a compiler warning: ginpostinglist.c:89:24: warning: result of comparison of constant 65536 with expression of type 'OffsetNumber' (aka 'unsigned short') is always true [-Wtautological-constant-out-of-range-compare] Assert(iptr->ip_posid < (1 << MaxHeapTuplesPerPageBits)); ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../../../src/include/c.h:784:10: note: expanded from macro 'Assert' Trap(!(condition), "FailedAssertion") ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../../../src/include/c.h:766:28: note: expanded from macro 'Trap' if ((assert_enabled) && (condition)) ^~~~~~~~~ 1 warning generated. Fix by commenting out the assertion with preprocessor blocks in an attempt to make future merge conflicts easier to resolve. A previous version of this patch was reviewed by Adam Berlin.
-
由 Adam Berlin 提交于
The level of TERSE or greater was set during development, we can lower this to DEBUG now that this feature has stablized.
-
由 Adam Berlin 提交于
It fails and appears to not be maintained when: --enable-gpfdist and --with-openssl are configured.
-
由 David Krieger 提交于
(cherry picked from commit 813528e7)
-
由 Jamie McAtamney 提交于
Because the gpinitstandby flag for passing in a standby master data directory was changed from -F to -S, this commit changes -F to -S in gpinitsystem to match. -S was already in use for specifying that the cluster should have its mirrors set up in spread configuration, so that flag is changed to --mirror-mode, which accepts the mirror mode ('group' or 'spread') as an argument. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Co-authored-by: NMark Sliva <msliva@pivotal.io> (cherry picked from commit 6fa3bce8)
-
- 04 4月, 2019 13 次提交
-
-
由 Jacob Champion 提交于
Despite my best efforts to avoid races on overloaded test containers, test_join_and_indicate_progress_prints_dots_until_pool_is_done() has been failing fairly often. Replace the simple-but-flaky time-based test with an implementation that serializes the components of the race. (cherry picked from commit 9f5384bc)
-
由 Lisa Owen 提交于
-
由 Chuck Litzell 提交于
* REASSIGN OWNED. edits. Remove qualification that it doesn't change the database ownership * ALTER FUNCTION. set from current clause description revision * COMMENT. capitalize proper noun. * COPY. describe PROGRAM option. * CREATE AGGREGATE. Implements new syntax. * CREATE FUNCTION. edits. * DROP ROLE. small edit, link to other commands * DROP USER. trivial edit. * PREPARE. small edits * REASSIGN OWNED. Trivial edits. * REINDEX. trivial edit. * pg_dump. use --quote-all-identifers for cross-version dumps * Additional edits * Updates from review * Updates from review
-
由 David Yozie 提交于
-
由 David Krieger 提交于
6_Backport: show gprecoverseg progress
-
由 Francisco Guerrero 提交于
- Read PXF host/port from environment variables - Add functions to get the PXF port and host - Add unit tests for get_pxf_port get_pxf_host We store the current value of the environment variable, then we set a custom host/port, run the tests, and finally restore the value of the environment variable. - Handle error when parsing PXF_PORT
-
由 Francisco Guerrero 提交于
- The transaction ID and segment ID are only used by a subset of profiles. PXF should be able to append the transaction and segment IDs depending on the profile using the header information. - Remove write_file_name, do not send path
-
由 Oliver Albertini 提交于
Co-authored-by: NOliver Albertini <oalbertini@pivotal.io> Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io>
-
由 Oliver Albertini 提交于
Previously was using master. Co-authored-by: NOliver Albertini <oalbertini@pivotal.io> Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io>
-
由 Adam Berlin 提交于
Postgres optimizes the storage of the ItemPointer in the Gin Posting List. It only stores 11 bits for the offset number because heap tables only have enough tuples per block to fit in 11 bits. However, Greenplum append-only tables store 16 bits worth of offset numbers. Initially we thought we'd need to modify decode_varbyte() but it turns out that it is OK. It handles 48 bits already. Co-authored-by: NAlexandra Wang <lewang@pivotal.com> Co-authored-by: NAshwin Agrawal <aagrawal@pivotal.io>
-
由 Adam Berlin 提交于
(cherry picked from commit 5e918bf6)
-
由 Chuck Litzell 提交于
* docs - remove gpsyncmaster and add pg_basebackup to backend program list. * Updates from review
-
由 Chuck Litzell 提交于
-
- 03 4月, 2019 16 次提交
-
-
由 Kalen Krempely 提交于
Make "demo_cluster" the default tag (ie: no tag). That is, when a scenario does not specify a behave tag it uses the demo cluster environment to run. Use the concourse_cluster tag if a scenario requires a remote cluster. Concourse runs the scenarios with no tag that use a demo cluster by filtering for --tags=~concourse_cluster. Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit 40028cf4)
-
由 David Krieger 提交于
Regenerate pipeline from CLI_BEHAVE_TESTS refactor. (cherry picked from commit 5dc3bfaa)
-
由 David Krieger 提交于
Renamed to CLI_BEHAVE_TESTS for clarity (cherry picked from commit 87c4a52c)
-
由 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 735da14f)
-
由 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 55add2c5)
-
由 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. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Authored-by: NKalen Krempely <kkrempely@pivotal.io> (cherry picked from commit ffce7734)
-
由 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)
-