- 27 5月, 2016 4 次提交
-
-
由 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
-
- 19 5月, 2016 11 次提交
-
-
由 Andreas Scherbaum 提交于
This will no longer spill logfiles from the demo cluster into the users ~/gpAdminLogs directory. Also it makes it easier to identify which logfile was created by the last regression test run. Closes #689 Closes #523
-
由 Adam Lee 提交于
To get fast feedback. Also deleted some dead codes and improved tests for s3conf.
-
由 Adam Lee 提交于
-
由 Adam Lee 提交于
-
由 Pengzhou Tang 提交于
dispatcher/ directory This commit has no logic change, it just contains movement of code across files, to make dispatcher code clearer, and easier for unit testing. Signed-off-by: Kenan Yao
-
-
由 Adam Lee 提交于
Usage: s3chkcfg -c "s3://endpoint/bucket/prefix config=path_to_config_file", to check the configuration. s3chkcfg -d "s3://endpoint/bucket/prefix config=path_to_config_file", to download and output to stdout. s3chkcfg -t, to show the config template. s3chkcfg -h, to show this help. Also did refactoring to reuse functions common with s3ext module.
-
由 Shreedhar Hardikar 提交于
-
由 Daniel Gustafsson 提交于
-
由 Daniel Gustafsson 提交于
The codegen-prefix path list is semicolon separated and must thus be quoted when passed to autoconf as it otherwise breaks up the commandline. Add missing quote character in the README documentation.
-
-
- 18 5月, 2016 5 次提交
-
-
由 Heikki Linnakangas 提交于
There were a bunch of changes vs. upstream in the way the PGPROC free list was managed, and the way backend exit was handled. They seemed largely unnecessary, and somewhat buggy, so I reverted them. Avoiding unnecessary differences makes merging with upstream easier too. * The freelist was protected by atomic operations instead of a spinlock. There was an ABA problem in the implementation, however. In Prepend(), if another backend grabbed the PGPROC we were just about to grab for ourselves, and returned it to the freelist before we iterate and notice, we might set the head of the free list to a PGPROC that's actually already in use. It's a tight window, and backend startup is quite heavy, so that's unlikely to happen in practice. Still, it's a bug. Because backend start up is such a heavy operation, this codepath is not so performance-critical that you would gain anything from using atomic operations instead of a spinlock, so just switch back to using a spinlock like in the upstream. * When a backend exited, the responsibility to recycle the PGPROC entry to the free list was moved to the postmaster, from the backend itself. That's not broken per se, AFAICS, but it violates the general principle of avoiding shared memory access in postmaster. * There was a dead-man's switch, in the form of the postmasterResetRequired flag in the PGPROC entry. If a backend died unexpectedly, and the flag was set, postmaster would restart the whole server. If the flag was not set, it would clean up only the PGPROC entry that was left behind and let the system run normally. However, the flag was in fact always set, except after ProcKill had already run, i.e. when the process had exited normally. So I don't see the point of that, we might as well rely on the exit status to signal normal/abnormal exit, like we do in the upstream. That has worked fine for PostgreSQL. * There was one more case where the dead-man's switch was activated, even though the backend exited normally: In AuxiliaryProcKill(), if a filerep subprocess died, and it didn't have a parent process anymore. That means that the master filerep process had already died unexpectedly (filerep subprocesses are children of the are not direct children of postmaster). That seems unnecessary, however: if the filerep process had died unexpectedly, the postmaster should wake up to that, and would restart the server. To play it safe, though, make the subprocess exit with non-zero exit status in that case, so that the postmaster will wake up to that, if it didn't notice the master filerep process dying for some reason. * HaveNFreeProcs() was rewritten by maintaining the number of entries in the free list in a variable, instead of walking the list to count them. Presumably to make backend startup cheaper, when max_connections is high. I kept that, but it's slightly simpler now that we use a spinlock to protect the free list again: no need to use atomic ops for the variable anymore. * The autovacFreeProcs list was not used. Autovacuum workers got their PGPROC entry from the regular free list. Fix that, and also add missing InitSharedLatch() call to the initialization of the autovacuum workers list.
-
-
由 Shreedhar Hardikar 提交于
This is specially useful for using to get a pointer to a member in a structure that is an embedded array.
-
由 Shreedhar Hardikar 提交于
-
由 Chumki Roy 提交于
-