- 17 8月, 2017 6 次提交
-
-
由 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 23 次提交
-
-
由 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 提交于
-
由 Heikki Linnakangas 提交于
CopyRelPath() is essentially a copy of relpath(), but it returns the result in a caller-supplied buffer instead of pallocing. That's redundant, and the calls are not in performance-critical path, so let's just use relpath() and get rid of CopyRelPath(). This reduces our diff footprint vs upstream. If there were upstream changes to relpath(), we would surely forget to make the same changes to CopyRelPath().
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Richard Guo 提交于
Resource group DDL is supposed to be executed by DBA and usually will not be in an explicit transaction with other statements. To reduce the complexity of resource group, resource group DDL is designed cannot run inside transaction block, sub-transaction, function or multi-command string. Signed-off-by: NZhenghua Lyu <zlv@pivotal.io>
-
由 David Yozie 提交于
-
由 mkiyama 提交于
-
由 mkiyama 提交于
-
由 Asim R P 提交于
Signed-off-by: NXin Zhang <xzhang@pivotal.io>
-
由 mkiyama 提交于
DOCS: External table - gpfdist or file protocol w/named pipe data source allows only 1 reader. From 4.3.x
-
由 mkiyama 提交于
-
由 Alexander Denissov 提交于
-
由 mkiyama 提交于
-
由 Heikki Linnakangas 提交于
Upstream commit cd902b33, from 8.4, changed StoreAttrDefault function's adbin argument from a string to a Node *. We had backported that, but the code to deal with it inside the function was not 100% identical to the upstream version. There was nothing wrong with the way it was written in GPDB per se, but let's make it identical to the upstream version anyway, to avoid merge conflicts.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
It will be re-introduced in 8.4, but it's unused now.
-
由 Heikki Linnakangas 提交于
-
由 Ashwin Agrawal 提交于
Currently, isolation2 vacuum_cleanup test was using base AO/CO tables for validating if age drops down. Actaully the test should check auxiliary tables. As anyways relfrozenxid doesn't carry any weigth for AO/CO base table.
-
由 Ashwin Agrawal 提交于
AO and CO tables never store transactionIds and persistent table always have tuples with FrozenXid only. Hence these tables should not have valid relfrozenxid, hence also should not matter for age calculation. Persistent tables are currently skipped internally from `datfrozenxid` calculation but still contained valid value for relfrozenxid in pg_class. Whereas AO/CO tables carried valid relfrozenxid and were used for `datfrozenxid` calculation as well. This commit makes sure only tables involved in `datfrozenxid` calculation, actually carry valid relfrozenxid in pg_class and others don't. So, externally someone executing age() function can easily ignore such tables by checking `not relfrozenxid = 0`. Fixes #2856.
-
由 Jimmy Yih 提交于
When running pg_regress, sometimes you may want to exclude certain tests from your schedule file from running. Before, you would have to modify the schedule file to comment/ignore out the unwanted test. Now we can do it from command line with --exclude-tests option that is space and comma delimited. Example: ./pg_regress --exclude-tests="test1 test2,test3 ... testN" Authors: Abhijit Subramanya and Jimmy Yih
-
由 Chuck Litzell 提交于
* Add ignore_checksum_failure GUC to reference * Changes for review comments * Promote embedded warning to a tagged warning
-
由 Alexander Denissov 提交于
-
- 15 8月, 2017 9 次提交
-
-
由 Heikki Linnakangas 提交于
* Remove unnecessary "use" directives. Importing modules adds some overhead. * Use File::Temp instead of POSIX.tmpnam for creating temporary files. File::Temp is used in atmsort.pm anyway, so also using it in explain.pm doesn't add extra overhead, like the otherwise-unused POSIX module does. The File::Temp API actually fits our needs better, so this shortens the code. And it allows removing the "use POSIX" directives, which again reduces the overhead of starting up the program. * Use perl's built-in grep function, instead of launching the external grep program. Launching a new process is more expensive. Altogether, these changes shave maybe 5-10 ms off the startup time of gpdiff.pl, out of about 60 ms. That's not a huge difference, but every little helps, and this is nice clean up in any case.
-
由 Heikki Linnakangas 提交于
In PostgreSQL, we always just use 'diff', even on Solaris. Should be good enough for GPDB too. (We don't officially even support Solaris anymore.)
-
由 Zhenghua Lyu 提交于
The quote_string function will make sure that the value(if type is string) is enclosed by `'`. This is introduced in previous commit(f936c4f3). We need to make the change of gp_resource_manager meet the logic now.
-
由 Larry Hamel 提交于
Follow up commit for f936c4f3, which added quotes around gpconfig values. Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Heikki Linnakangas 提交于
There are better ways to set block size and table type, like with the gp_default_storage_options GUC.
-
由 Heikki Linnakangas 提交于
-
由 Alexander Denissov 提交于
Signed-off-by: NLav Jain <ljain@pivotal.io> Signed-off-by: NOleksandr Diachenko <odiachenko@pivotal.io> Signed-off-by: NShivram Mani <smani@pivotal.io> Signed-off-by: NJohn Gaskin <jgaskin@pivotal.io> Signed-off-by: NAlexandra Wang <lewang@pivotal.io>
-
由 Marbin Tan 提交于
Signed-off-by: NNadeem Ghani <nghani@pivotal.io>
-
由 Nadeem Ghani 提交于
When you use gpconfig, users were forced to double quote the guc values. For example: Prior: gpconfig -c pljava_classpath -v "'examples.jar'" Now: gpconfig -c pljava_classpath -v 'examples.jar' or gpconfig -c pljava_classpath -v examples.jar Enhancement: Now all GUCs with vartype string will be wrapped in single quotes before being written to the postgresql.conf. Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
- 14 8月, 2017 2 次提交
-
-
由 Ning Yu 提交于
Now we support the resgroup memory_limit memory_shared_quota alteration in below syntax: ALTER RESOURCE GROUP <group> SET MEMORY_SHARED_QUOTA <value>; ALTER RESOURCE GROUP <group> SET MEMORY_LIMIT <value>; The new value may take effect immediately if the actual shared memory usage is lower than the new value; otherwise it will delay the effect. Signed-off-by: NHaisheng Yuan <hyuan@pivotal.io>
-
由 Ning Yu 提交于
* resgroup: increase max slots for isolation tests. * ICW: ignore resgroup related warnings. * ICW: try to load resgroup variant of answers when resgroup enabled. * ICW: provide resgroup variant of answers. * ICW: check whether resqueue is enabled in UDF. * ICR: substitude usrname in gpconfig output. * ICR: explicitly set max_connections. * isolation2: increase resgroup concurrency for max_concurrency tests.
-