- 30 8月, 2017 16 次提交
-
-
由 Tom Meyer 提交于
Original commit message: This speeds up reassigning locks to the parent owner, when the transaction holds a lot of locks, but only a few of them belong to the current resource owner. This is particularly helps pg_dump when dumping a large number of objects. The cache can hold up to 15 locks in each resource owner. After that, the cache is marked as overflowed, and we fall back to the old method of scanning the whole local lock table. The tradeoff here is that the cache has to be scanned whenever a lock is released, so if the cache is too large, lock release becomes more expensive. 15 seems enough to cover pg_dump, and doesn't have much impact on lock release. Jeff Janes, reviewed by Amit Kapila and Heikki Linnakangas.
-
由 Shivram Mani 提交于
-
由 dyozie 提交于
-
由 dyozie 提交于
-
由 Nadeem Ghani 提交于
Remove global variable table_expand_error by checking the pool of done ExpandCommand(s). Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Shoaib Lari 提交于
This commit adds a check for cluster state, heap_checksum setting on all primary segments match heap_checksum setting on master, before doing the expansion. If all primaries match the master, gpexpand continues with setting up expansion segments. Otherwise, it logs the inconsistent primaries and exits. Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Nadeem Ghani 提交于
gpexpand had a lot of code in the __main__ module method, along with global vars used by other methods and classes in the module. This commit introduces a main() method, which can be called from unit tests, and converts global vars to params and fields. Signed-off-by: NShoaib Lari <slari@pivotal.io>
-
由 Shoaib Lari 提交于
Signed-off-by: NNadeem Ghani <nghani@pivotal.io>
-
由 Mel Kiyama 提交于
* DOCS: gucs for interconnect debugging * docs: port fixes from COPY ON SEGMENT review.
-
由 Jacob Champion 提交于
The recipe didn't properly chain the $(MAKE) invocations; any failures when building or installing gpcloud were ignored.
-
由 Heikki Linnakangas 提交于
It was getting in the way of backporting commit 9b1b9446f5 from PostgreSQL, which added an '#include "storage/lock.h"' to resowner.h, forming a cycle. The include was only needed for the decalaration of awaitedOwner global variable. Replace "ResourceOwner" with the equivalent "struct ResourceOwnerData *" to avoid it. This revealed a bunch of other files that were relying on resowner.h being indirectly included through lock.h. Include resowner.h directly in those files. The ResPortalIncrement.owner field was not used for anything, so instead of including resowner.h in that file, just remove the field that needed it.
-
由 Xin Zhang 提交于
An FTS probe to the primaries in a mirrorless cluster will never result in the update of gp_segment_configuration. If a primary goes down, we must keep the primary marked as up so that gpstart can start the primary back up. All transactions will abort and nothing should work except for read-only queries to master-only catalog tables. Stopping the FTS probes for mirrorless cluster introduced an infinite loop in FtsNotifyProber in which the dispatcher waits in an infinite loop for fts_statusVersion to change. To break the infinite loop, we acknowledge the forced probe request as a no-op and update fts_statusVersion to break the loop for the dispatcher. The dispatcher should then act same as before this commit. We also add #define for character value of GpFaultStrategy. Authors: Xin Zhang, Ashwin Agrawal, and Jimmy Yih
-
由 Lav Jain 提交于
* Refactor GPHDFS regression to run for pxf * remove customized Hadoop home location
-
由 Todd Sedano 提交于
We believe the pipeline is red due to this commit: https://github.com/greenplum-db/gpdb/commits/fdc9e0a2812dbb01f0883c570f90d82397e2c573 The PR pipeline is red when it was pushed: https://github.com/greenplum-db/gpdb/pull/3089
-
由 Mel Kiyama 提交于
* DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes * docs: remove draft comment * docs: Edited text based on review comments. Reorganized notes on COPY ... ON SEGMENT information. * docs: clean up typos found in review.
-
由 David Yozie 提交于
* porting hstore contrib module docs from postgres 8.4 * adding link to hstore doc from data type refernce * adding placeholder install instructions * removing info about GIN index support
-
- 29 8月, 2017 19 次提交
-
-
由 Weinan WANG 提交于
Some unreentrant functions are invoked in signal handler. To fix this bug: change signal handler to asynchronous modle. using global variable "sig_flag" to store last signal state,every 1s polling or after failed happen in block IO function(such as send/ receive) check "sig_flag". fix bug : gpload does not stop after informatica sends exit call Some unreentrant functions are invoked in signal handler. To fix this bug: change signal handler to asynchronous modle. using global variable "sig_flag" to store last signal state,every 1s polling or after failed happen in block IO function(such as send/ receive) check "sig_flag".
-
由 Heikki Linnakangas 提交于
Introduced by commit 522c7c09, spotted by Coverity.
-
由 Heikki Linnakangas 提交于
In PostgresQL, the DO block is after RemoveFuncStmt. It was slightly misplaced when it was backported from PostgreSQL 9.0.
-
由 Daniel Gustafsson 提交于
Any error that the user is expected to see should be using the ereport() macro rather than its older cousin elog(). Also avoid closing resources just before erroring out as the error cleanup will be handled automatically, and move a long message to have an errhint instead.
-
由 Pengzhou Tang 提交于
In binary swap test, new binary is replaced by old binary and then run pg_dump, however, pg_dump will still try to load new regress.so, so if regress.so contain new symbols only belong to new binary, it will report an error. For resGroupPalloc() ifself, IsResGroupEnabled or IsResGroupActivated make no much difference, so to make binary swap pass, we still use IsResGroupEnabled.
-
由 Heikki Linnakangas 提交于
This means that hstore will be compiled and installed by a top level "make", and the regression tests are run as part of "make installcheck-world".
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
To make the regression tests pass on GPDB, where we have standard_conforming_strings=on by default. This is a cherry-pick of upstream commit: commit 0e22e08f Author: Robert Haas <rhaas@postgresql.org> Date: Tue Jul 20 01:22:52 2010 +0000 Make hstore regression tests independent of standard_conforming_strings. Per buildfarm.
-
由 Heikki Linnakangas 提交于
Our GIST version doesn't pass the 'recheck' argument to 'consistent' functions yet. That will come in commit 9b5c8d45, as part of the PostgreSQL merge.
-
由 Heikki Linnakangas 提交于
I'm not sure if we broke this during the 8.3 merge, or if it was broken even before that, but our version of heap_form_tuple was confused over what the isnull argument is. The difference between heap_form_tuple() and heap_formtuple() is the values used in the "isnull" array, but our heap_form_tuple passed a 'char' array to the internal heap_fill_tuple() function, which assumes a 'bool' arry. That caused an assertion failure in hstore regression tests (and almost certainly a crash or at least wrong results without assertions, though I didn't check.) To fix, take the version of heap_form_tuple() from PostgreSQL 8.4, which converts the 'char' array to a 'bool' array, and then calls the new heap_formtuple() function.
-
由 Pengzhou Tang 提交于
SPIMemReserved was initialized in CreateSharedMemoryAndSemaphores which make no sense, this commit put it under InitResManager where the resource memory policy is set.
-
由 Heikki Linnakangas 提交于
As a pleasent side-effect, the window specification in a "func_expr OVER (window_spec)" rule now gets its parse location set correctly. Thanks to that, a few error messages now give a user-friendly error location line.
-
由 Heikki Linnakangas 提交于
GPDB 5 doesn't have the pg_get_functiondef server function needed by \ef, so it doesn't work. Fixes github issue #3076. This is a backport of an upstream commit that conveniently fixes this: commit 2463f5da3ccd67b266ee7a9b8c0906221a501b9e Author: Tom Lane <tgl@sss.pgh.pa.us> Date: Thu Nov 10 18:37:05 2011 -0500 Throw nice error if server is too old to support psql's \ef or \sf command. Previously, you'd get "function pg_catalog.pg_get_functiondef(integer) does not exist", which is at best rather unprofessional-looking. Back-patch to 8.4 where \ef was introduced. Josh Kupershmidt
-
由 Pengzhou Tang 提交于
The resource group is enabled but not initialized on auxiliary processes and special backends like ftsprobe and filerep, previously we performed resource group operations no matter resource group is initialized or not which leads to some unexpected error.
-
由 Pengzhou Tang 提交于
-
由 Xiaoran Wang 提交于
Signed-off-by: NXiaoran Wang <xiwang@pivotal.io> Signed-off-by: NAdam Lee <ali@pivotal.io>
-
由 Chuck Litzell 提交于
* Correct the maximum content id to be number of segments less 1 * Fix additional places that suggest content id are numbered from 1.
-
由 Nadeem Ghani 提交于
Previously, we were only checking localhost for standby heap checksum in gpstart. This is not the case as the standby is usually on a remote host. gpstart raises an error due to not finding the pg_control file of standby locally. Fixed by always doing a remote host call for the standby master. Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Omer Arap 提交于
Signed-off-by: NJemish Patel <jpatel@pivotal.io>
-
- 28 8月, 2017 5 次提交
-
-
由 Heikki Linnakangas 提交于
Use ereport(), with a proper error code, for errors that are "expected" to happen sometimes, like missing configuration files, or network failure. That's nicer in general, but the reason I bumped into this is that internal error messages include a source file name and line number in GPDB, and if those error messages are included in the expected output of regression tests, those tests will fail any time you do change the file, so that the elog() moves around and the line number changes.
-
由 Daniel Gustafsson 提交于
An assertion with a side effect may alter the main codepath when the tree is built with --enable-cassert, which in turn may lead to subtle differences due compiler optimizations and/or straight bugs in the side effect. Rewrite the assertions without side effects to leave the main codepath intact.
-
由 Pengzhou Tang 提交于
-
由 Pengzhou Tang 提交于
This commit verified that connections in utility mode should not be governed by resource group
-
由 Pengzhou Tang 提交于
This commit verified that cursors, prepare and statements within pl functions didn't trigger self-deadlock by the concurrency control of resource group.
-