- 19 8月, 2017 4 次提交
-
-
由 Taylor Vesely 提交于
This test checks PersistentObjLock is not acquired while holding io_in_progress lock on a buffer. Tests will pass if PersistentObjLock is not acquired. Signed-off-by: NAsim R P <apraveen@pivotal.io>
-
由 Jacob Champion 提交于
Signed-off-by: NTaylor Vesely <tvesely@pivotal.io>
-
由 Taylor Vesely 提交于
Adds two new LW locks to protect filespace and tablespace hash tables to disambiguate them from PersistentObjLock. Previously, PersistentObjLock was overloaded to both protect these hash tables along with persistent heap tables. If two backends try to flush the same dirty buffer, a deadlock could potentially arise in which backend 1 holds PersistentObjLock and requests io_in_progress lock of the buffer to be evicted. Backend 2 holds io_in_progress lock on the same buffer and attempts to obtain file path. Because the file path is in hash tables protected by PersistentObjLock, backend 2 requests PersistentObjLock and blocks due to backend 1. Signed-off-by: NAsim R P <apraveen@pivotal.io>
-
由 Asim R P 提交于
Comments were copied from the add node code path and did not match their intent. This commit repairs the language of these comments to match their behavior. Signed-off-by: NTaylor Vesely <tvesely@pivotal.io>
-
- 18 8月, 2017 20 次提交
-
-
由 Heikki Linnakangas 提交于
To match upstream more closely, hopefully avoiding some silly merge conflicts in the future.
-
由 Heikki Linnakangas 提交于
extent -> extend. And reformat.
-
由 Heikki Linnakangas 提交于
Remove premature optimization in create_indexscan_plan, where we stripped RestrictInfo decorations while we iterated through the list. That was premature, because while it works, order_qual_clauses() can make use of the information in the RestrictInfo, if it's still present. This reverts that piece of code to the way it is in the upstream. I'm not sure if this makes any observable difference, but let's be tidy in any case. Also, reorder the extract_actual_clauses and order_qual_clauses calls in create_ctescan_plan, so that order_qual_clauses is called first. For the same reason.
-
由 Heikki Linnakangas 提交于
I repurposed the existing psql_gpdb_du test for this. It was very small, I think we can put tests for other \d commands in the same file. In the passing fix a typo in a comment there, and move the expected output from output/ to expected/, because it doesn't need any string replacements.
-
由 Heikki Linnakangas 提交于
The \dx+ command requires pg_describe_object() function, which we don't have in GPDB yet. Until then, treat \dx+ the same as \dx. Note that this code is written such that \dx+ can still be used, when connected to a PostgreSQL 9.1 or later server. Not that we particularly care about that case, but might as well. Per github issue #2574.
-
由 Xiaoran Wang 提交于
When there is \t between 'ON' and 'SEGMENT' , client can give right error message. Signed-off-by: NXiaoran Wang <xiwang@pivotal.io>
-
由 xiong-gang 提交于
resgroup: allow memory related alteration to take effect progressively. memory_limit, memory_shared_quota and concurrency might be altered concurrently when there're transactions running in the resource group, these changes cannot take effect immediately. Release memory 1)at the end of the 'ALTER' transaction 2)when a resource group slot get freed. Acquire memory at the beggning of a transaction if the resource group dosen't have enough memory as configured.
-
由 Larry Hamel 提交于
- validate consistent checksum settings - Make sure checksum settings for all segments are same as master - Add logging proxy to allow logging to file to have different contents than stdout - Do heap checksum only for when starting up all segments. - Add option --skip-heap-checksum-validation - If this option is provided to gpstart, the cluster will start up without checking for matching "data_checksums" GUC between master and segments. Signed-off-by: NNadeem Ghani <nghani@pivotal.io> Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Larry Hamel 提交于
-
由 Nadeem Ghani 提交于
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>
-
由 Marbin Tan 提交于
Signed-off-by: NLarry Hamel <lhamel@pivotal.io> Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Marbin Tan 提交于
We were passing an empty list and appending it instead of extending it. using an empty list as a default value for a function parameter is an anti-pattern. Python behaves unintuitively, where it creates a single instance of the variable and uses it again. Feels like how a static variable would behave in c. Signed-off-by: NNadeem Ghani <nghani@pivotal.io>
-
由 Jimmy Yih 提交于
As we develop segment WAL replication, we need a green to green CI pipeline that we can start small and add relative jobs from gpdb_master as we add more functionality. This commit establishes that pipeline and omits ICW tests that are currently not supported by segment WAL replication. Authors: Abhijit Subramanya and Jimmy Yih
-
由 Larry Hamel 提交于
- the params given to an invocation of gpconfig may be returned by sys.argv as including a list, so parse appropriately. Signed-off-by: NShoaib Lari <slari@pivotal.io>
-
由 Nadeem Ghani 提交于
Updating the log message to display the parameters gpconfig was called with, both if the GUC was changed successfully or not. Signed-off-by: NMarbin Tan <mtan@pivotal.io> Signed-off-by: NShoaib Lari <slari@pivotal.io> Signed-off-by: NLarry Hamel <lhamel@pivotal.io>
-
由 Lei Wang 提交于
-
由 Alex Wang 提交于
This commit removes the duplicate line in the 'pg_proc.sql' which causes OID 6065 to get used twice. Signed-off-by: NAlex Wang <alex@awakesecurity.com>
-
由 Heikki Linnakangas 提交于
If you have a simple insert, like "INSERT INTO foo VALUES ('bar')", we evalute the target list (i.e. 'bar') in the master, and route the insert to the correct partition and segment, based on the constants. However, there was a mismatch between allConstantValuesClause(), and what its callers assumed. The callers assumed that if allConstantValuesClause() returns true, the target list contains only Const nodes. But in reality, allConstantValuesClause() also returned true, if there were non-volatile function expressions in the target list, that could be evaluated, and would then produce a constant result. Fix the mismatch, by making allConstantValuesClause() be more strict, so so that it only returns true if all the entries are true Consts. Fixes github issue #285, reported by @liruto.
-
由 Heikki Linnakangas 提交于
It almost seems like when we merged with PostgreSQL 8.2 (sic), we missed this one line from commit 986085a7. Before that, the rowMarks list was a list of integers, but now it's a list of RowMarkClauses.
-
由 Jane Beckman 提交于
* Add table entries for rolcreaterexthdfs, rolcreatewexthdfs * Change to gphdfs protocol * typo
-
- 17 8月, 2017 14 次提交
-
-
由 Chuck Litzell 提交于
* Expand description of data_checksums GUC to include checksum behavior and scope. * Mention that failed checksum verification prevents mirroring corrupted data.
-
由 Heikki Linnakangas 提交于
Commit e40e78fa added the "unused" attribute to the function, but it didn't have any effect. It seems that for a function that returns a pointer, the attribute must be placed before the "*" indicating that the return type is a pointer. Go figure..
-
由 Heikki Linnakangas 提交于
This silences a compiler warning: regress.c:2884:7: warning: implicit declaration of function ‘IsResGroupEnabled’ [-Wimplicit-function-declaration]
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
Per discussion at https://github.com/greenplum-db/gpdb/pull/2379, we don't really need to use a special, patched, version of Xerces-C. Remove the check.
-
由 Heikki Linnakangas 提交于
This allows removing all the code in CTranslatorDXLToPlStmt that tracked the parent of each call. I found the plan node IDs awkward, when I was hacking on CTranslatorDXLToPlStmt. I tried to make a change where a function would construct a child Plan node first, and a Result node on top of that, but only if necessary, depending on the kind of child plan. The parent plan node IDs made it impossible to construct a part of Plan tree like that, in a bottom-up fashion, because you always had to pass the parent's ID when constructing a child node. Now that is possible.
-
由 Adam Lee 提交于
1, remove unnecessary web tables 2, add various distribution with `ON SEGMENT` tests 3, add zero column with `ON SEGMENT` tests
-
由 David Yozie 提交于
-
由 Lei Wang 提交于
Signed-off-by: NAlexandra Wang <lewang@pivotal.io>
-
由 Nadeem Ghani 提交于
Previously, the "all" target was used only by gpMgmt/bin/Makefile in place of the "install" target used elsewhere. The underlying reason was because python doesn't need a compile phase (the "all" target). However, this is inconsistent. Change to use the standard "install" target, which is also the default on the gpMgmt/bin/Makefile. Signed-off-by: NLarry Hamel <lhamel@pivotal.io>
-
由 Divya Bhargov 提交于
Signed-off-by: NJingyi Mei <jmei@pivotal.io>
-
由 Tom Lane 提交于
Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVersion(). It's desirable to get this into the field and back-patched ASAP, so that older clients are more likely to understand the new server version numbering by the time any such servers are in the wild. (The results with an old client would probably not be catastrophic anyway for a released server; for example "10.1" would be interpreted as 100100 which would be wrong in detail but would not likely cause an old client to misbehave badly. But "10devel" or "10beta1" would result in sversion==0 which at best would result in disabling all use of modern features.) Extracted from a patch by Peter Eisentraut; comments added by me Patch: <802ec140-635d-ad86-5fdf-d3af0e260c22@2ndquadrant.com>
-
由 Jane Beckman 提交于
- 16 8月, 2017 2 次提交
-
-
由 Pengzhou Tang 提交于
gp_resgroup_memory_policy is recently introduced by resource group module, so when running binary swap cases, the old binary can not recognize it, so remove it to make cases pass
-
由 Heikki Linnakangas 提交于
-