- 02 6月, 2016 2 次提交
-
-
由 Heikki Linnakangas 提交于
We don't particularly care about performance on Solaris at the moment, and have no Solaris systems to test on. Let's just rely on the upstream defaults, and revert this change to reduce our diff footprint vs. upstream.
-
-
- 01 6月, 2016 8 次提交
-
-
由 Dan Lynch 提交于
-
由 Heikki Linnakangas 提交于
If a page has hint bits set, but the buffer has not been marked as dirty, and it gets evicted between the 1st and 2nd vacuum pass, the 2nd pass gets upset. That can't happen in the upstream, as setting a hint bit always marks the buffer as dirty, but that is not guaranteed in GPDB, because of gp_disable_tuple_hints.
-
由 Shreedhar Hardikar 提交于
Includes tests: composite_keys_gpdb_1 composite_keys_gpdb_3 composite_keys_gpdb_2 partitionindexes staticselection cte_functest cte_queries create_table_default_distribution lastj lastj_hash indexapply
-
由 Heikki Linnakangas 提交于
Commit 33a1278c merged upstream addition of a typmod argument to makeConst(). However, one of the calls was botched during the merge, and the typmod argument was inserted to wrong place in argument list. This seems to have been harmless because the constant ended up being NULL anyway, and the bogus values for the other arguments were ignored.
-
由 Heikki Linnakangas 提交于
These got in the way in the PostgreSQL 8.3 merge, so let's get them over with before the big merge lands.
-
由 Heikki Linnakangas 提交于
This makes no difference at runtime, as the argument is always passed as NULL anyway, but let's avoid unnecessary differences vs. upstream.
-
由 Heikki Linnakangas 提交于
These changes were lifted from upcoming PostgreSQL 8.3 merge branch, but are not related to the merge per se, so let's get them out of the way before the big merge lands. Plus other cosmetic things in neighbouring code that stuck my eye.
-
由 Heikki Linnakangas 提交于
-
- 29 5月, 2016 3 次提交
-
-
由 Heikki Linnakangas 提交于
A new regression test was added in the upstream that does work_mem='64kB', which used to fail without --enable-cassert. There's little reason to not allow a small value here, so let's just allow it. It doesn't mean that anyone should use such a small value in production, but that's just a matter of "don't do that then". The minimum was changed later in the upstream, too, to be 64 kb regardless of BLCKSZ.
-
由 Heikki Linnakangas 提交于
prev_item variable needs to be reset between the two loops. Otherwise, if the first item in the latter list (allocatedReaderGangs1) needs to be removed, things go wrong. I got an assertion failure with installcheck-good from that: FailedAssertion(""!(prev != ((void *)0) ? ((prev)->next) == cell : list_head(list) == cell)"", File: ""list.c"", Line: 616) This got broken in the recent refactoring commit 46dfa750. The rest of the changes in this commit, introducing the new next_item variable, wasn't needed for correctness, but IMHO makes the code easier to understand.
-
由 Heikki Linnakangas 提交于
I missed this in commit af7b1b51, which reverted the backend shutdown code closer to the upstream. Without it, auxiliary proc slots are never reused, so you run out of them fairly quickly, if any (non-permanent) auxiliary processes are used. Reported by Gang Xiong, who ran into this with gprecoverseg.
-
- 28 5月, 2016 2 次提交
-
-
由 Heikki Linnakangas 提交于
The checks for invalid TIDs are very cheap, a few CPU instructions. It's better to catch bugs involving invalid TID early, so let's always check for them. The LOGs in storeAttrDefault() that were also tied to this GUC seemed oddly specific. They were probably added long time ago to hunt for some particular bug, and don't seem generally useful, so I just removed them.
-
由 Jamie McAtamney 提交于
Previously, the functions and subclasses in gpcrondump, gpdbrestore, dump.py, and restore.py all required long lists of arguments to be passed around and required many helper functions. This made adding new command-line options or new features quite time-consuming to implement and to test. Now, a Context class has been added to backup_utils.py that holds all of the variables used for command-line options, as well as other variables used in many places during backup and restore; additionally, many helper functions have been condensed into a few functions within Context, and in the future more such functions can be moved to Context as needed. This will make it much easier to expand dump and restore functionality going forward.
-
- 27 5月, 2016 5 次提交
-
-
由 Kenan Yao 提交于
-
由 Kenan Yao 提交于
-
由 Shreedhar Hardikar 提交于
This way we can reuse the csv files in other installcheck suites.
-
由 Asim R P 提交于
Caught by access_methods/indexscan TINC tests.
-
-
- 26 5月, 2016 1 次提交
-
-
由 Daniel Gustafsson 提交于
This seems like a copy-paste error since the IDENTIFICATION marker is a PostgreSQL artifact and Peter Eisentraut probably didn't write the gpopt Makefile. Remove to make it look like the headers in other GPDB specific makefiles.
-
- 25 5月, 2016 4 次提交
-
-
由 Adam Lee 提交于
-
由 Adam Lee 提交于
-
由 Lubomir Petrov 提交于
-
由 Marbin Tan 提交于
-
- 24 5月, 2016 3 次提交
-
-
由 Daniel Gustafsson 提交于
This commit addresses the pg_restore documentation which was overlooked in the original commit 0b28e753 where pg_dump and pg_dumpall were fixed.
-
由 Adam Lee 提交于
Refactor s3common codes and add unit tests. Author: Adam & Yandong
-
由 Nikos Armenatzoglou 提交于
Enhacing code generated ExecVariableList with support of null attributes. Also, there are some formatting changes based on Google C++ style.
-
- 23 5月, 2016 1 次提交
-
-
由 Daniel Gustafsson 提交于
-
- 21 5月, 2016 4 次提交
-
-
由 Gang Xiong 提交于
1) add one new type of gang: singleton reader gang. 2) change interface of allocateGang. 3) handling exceptions during gang creation: segment down and segment reset. 4) cleanup some dead code.
-
由 Shreedhar Hardikar 提交于
-
由 Shreedhar Hardikar 提交于
-
This closes #764
-
- 20 5月, 2016 7 次提交
-
-
-
由 Daniel Gustafsson 提交于
The -i option is a noop in pg_dump and pg_dumpall, remove documentation from reference page. Andreas Scherbaum
-
由 Daniel Gustafsson 提交于
Make the description text match the summary.
-
由 Daniel Gustafsson 提交于
This attempts to clean up the autoconf script a bit and follow the upstream division of generic code in config/ with the actual lookup configuration in configure.in. Also updated our installation to rely on a more modern version of autoconf by backporting parts of upstream commit 7cc514ac. This commit consist of: * Decouple --enable-codegen and --with-codegen-prefix to not silently ignore prefixes if the enable flag isn't passed. Emit a warning if configuring prefixes without codegen. Also moves --with-codegen-prefix to require an argument since --with-codegen-prefix without an argument is likely to hide either a scripting bug or a misunderstanding from the user * Move program checks for cmake and apr-1-config to programs.m4 and allow for path overrides and ensure to use the resolved path when invoking cmake for --enable-codegen * Propagate the apr-1-config flags and objects to where used via Makefile.global rather than performing another lookup * Remove check for unused arguments since autoconf does that automatically since 2.63 * Remove backported fseeko handling since that isn't relevant for modern autoconf versions * Minor help output tidying and spelling fixes
-
由 Adam Lee 提交于
-
由 Pengcheng Tang 提交于
information. Authors: Christopher Hajas, Pengcheng Tang
-
由 Pengcheng Tang 提交于
If peer of failed segment is in ChangeTrackingDisabled state, its change tracking log is corrupted. This commit is for gprecoverseg to stop recovering such segments in incremental mode, instead it warns user to run a full recovery. Also enable gprecoverseg unit and behave tests. Authors: Pengcheng Tang, Chumki Roy, Christopher Hajas
-