- 28 3月, 2019 8 次提交
-
-
由 Chuck Litzell 提交于
-
由 David Yozie 提交于
-
由 Zhenghua Lyu 提交于
BuildPartitionNodeFromRoot will always use root relid no matter what parameter is passed to it. There is an optimization we might do: for some cases, like if user directly insert into a child partition, then set estate->es_result_partitions to NULL to avoid dispatch it since a huge partition table's partition info may cost much memory. We can spike this later.
-
由 Paul Guo 提交于
Previously the default value is 0, so normally log rotation happens each day by default according to the other log related guc configurations. That often makes a single log file rather large in real users' environment. Limiting the log file size so that people could easiler open and search the log files. Reviewed-by: NDaniel Gustafsson <dgustafsson@pivotal.io>
-
由 Paul Guo 提交于
1) pm_launch_walreceiver was introduced in b824fe8f to avoid a potential deadlock when cluster is down after updating the new role in gp_segment_configuration but before sending promote signal. It is buggy now since some changes. We need to put pm_launch_walreceiver in shared memory since it's used in different processes. 2) The following assertion is not always true in a real scenario if the segment is being promoted. We could simply stop the connection for the !am_mirror case. ProcessStartupPacket() if (am_ftshandler) { Assert(am_mirror); Ning Yu and we had some discussions for these bugs. He contributed for issue 1 also. Co-authored-by: NHaozhou Wang <hawang@pivotal.io>
-
由 Pengzhou Tang 提交于
Fts probe didn't report an error if it failed to resolve the DNS, so fts probe can mark those segments as down. Previously, DNSLookupAsError was only set to false in readCdbComponentInfoAndUpdateStatus(), however, codes keep coming and evolving, fts probe may set DNSLookupAsError to true in other code paths. To avoiding fts probe report a DNS error unexpectedly, use am_ftsprobe only to determine it and hide the DNSLookupAsError from callers.
-
由 Bhuvnesh Chaudhary 提交于
-
由 Bhuvnesh Chaudhary 提交于
-
- 27 3月, 2019 11 次提交
-
-
由 Daniel Gustafsson 提交于
Commit ea9df812 relaxes the requirement that all LWLocks are in a single array, which broke the LOCK_DEBUG code for trying to acquiring an LWLock. This is a meatball surgery attempt at making it at least compile and run, without trying to reinvent the old usecase. Minor tweaking of the code is also done to make LOCK_DEBUG cases be identified identically. Reported-by: Simon Gao in Github issue #7251 Reviewed-by: Ashwin Agrawal
-
由 Daniel Gustafsson 提交于
The GPSMON_METRIC_MAX setting was only used for platforms where we couldn't link with libsigar (namely Solaris, making these defines even more redundant as they weren't applicable in the first case), and support for that has long since been ripped out so remove the useless defines too. Also remove a commented out variable while in there. Reviewed-by: NJimmy Yih <jyih@pivotal.io> Reviewed-by: NHeikki Linnakangas <hlinnakangas@pivotal.io>
-
由 Daniel Gustafsson 提交于
Reviewed-by: NDavid Yozie <dyozie@pivotal.io>
-
由 Daniel Gustafsson 提交于
Since Greenplum is now based on PostgreSQL 9.4, update links to the upstream documentation to refer to the 9.4 docset rather than older versions. Also fix a few mentions of 8.3(.23) in the text along with some spacing. Reviewed-by: NDavid Yozie <dyozie@pivotal.io>
-
由 Daniel Gustafsson 提交于
The search.cpan.org site has been discontinued and replaced with metacpan.org, fix by replacing all links in the documentation. There is an additional link in the testcode which will be fixed as we merge with upstream. Reviewed-by: NDavid Yozie <dyozie@pivotal.io>
-
由 Daniel Gustafsson 提交于
In all but a few places we referred to the upstream documentation as "PostgreSQL documentation", this fixes the few places where we had a different spelling. Reviewed-by: NDavid Yozie <dyozie@pivotal.io>
-
由 Lisa Owen 提交于
* docs - discuss pxf column projection * add note about filter serialization * column projection is always enabled * edits requested by david
-
由 Bradford D. Boyle 提交于
Related PR discussion: kmacoskey: Another piece of this can be removed with the same intention as the other removal. This line in the Makefile is related to a kfw snowflake dependency that was being vendored into the Clients/Loaders package as brought in by Ivy. Note the path, ext. It was dropped from Ivy by releng awhile ago, 2c6f4c9d#diff-271f398f0c07147024e7980737cddb7d . The cp here probably should have been removed along with the change to Ivy, but it was missed. It can be removed - but lets make sure the Clients team is aware. pf-qiu: I think it's safe to do this now. Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Sambitesh Dash 提交于
Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Sambitesh Dash 提交于
Since we have removed the Ivy dependency manager entirely from GPDB 6+, we do not need this code anymore. It used to copy Ivy-managed libraries into the Greenplum installation for packaging. Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
-
由 Alexandra Wang 提交于
INSERT needs to Lock the child table on QD, otherwise the following dead lock scenario may happen if INSERT runs concurrently with VACUUM drop phase on an AppendOnly partitioned table. 1. VACUUM on QD: acquired AccessExclusiveLock on the child table 2. INSERT on QE: acquired RowExclusiveLock on the child table 3. VACUUM on QE: waiting for AccessExclusiveLock on the child table 4. INSERT on QD: waiting for AccessShareLock at ExecutorEnd() on the child table, this is after QE sends back which child it inserted Note that in step 2, INSERT only locks the child table on QE, it does not lock the child table on QD in the previous code. This patch adds the lock on QD as well to prevent the above dead lock. Added `insert_while_vacuum_drop` and updated `partition_locking` to reflect the changes
-
- 26 3月, 2019 11 次提交
-
-
由 Adam Berlin 提交于
A warning message is displayed to a user that attempts to perform `pg_create_physical_replication_slot()` on any individual segment, including the master segment so that they are aware that this command is not made to be distributed to the entire cluster.
-
由 Teng zhang 提交于
-
由 Amil Khanzada 提交于
* Remove unused IVYREPO_ variables for CentOS 6/7 Ivy is no longer used for CentOS 6/7. Authored-by: NAmil Khanzada <akhanzada@pivotal.io> * Remove unused IVYREPO_ variables for Coverity Ivy is no longer used for CentOS 6/7 and will go away. The coverity pipeline is also puased at this point in time, but we'll clean this up now. Co-authored-by: NBradford D. Boyle <bboyle@pivotal.io> Co-authored-by: NAmil Khanzada <akhanzada@pivotal.io>
-
由 Lisa Owen 提交于
* docs - gpexpand.status_detail external_writable field * gpexpand.status tbl - updated col now timestamp without tz
-
由 Lisa Owen 提交于
* docs - organize contrib modules in ref guide * provides * insignificant edit
-
由 Lisa Owen 提交于
* docs - new pxf parquet write options * add bytes * line edit: the PXF -> PXF * Line edit: which -> that
-
由 Lisa Owen 提交于
-
由 Lisa Owen 提交于
* docs - describe pxf jdbc profile QUOTE_COLUMNS option * clarify per comment from ivan
-
由 Chuck Litzell 提交于
* ALTER TABLE. Edits and fix example. * ALTER TYPE. Add IF NOT EXISTS and edits * ALTER VIEW. edits and add examples * clusterdb. small edit * CREATE EXTENSION. Edits mostly applied earlier. * CREATE FUNCTION. Compatibility edit. * CREATE RULE. Edits * EXPLAIN. small edits. * DROP RULE. minor edits * GRANT. revise server USAGE privilege description. * pg_restore. lots of edits. doesn't read PGDATABASE envvar. * REASSIGN OWNED. edits. Remove qualification that it doesn't change the database ownership * REASSIGN OWNED. edits. Remove qualification that it doesn't change the database ownership * Remove extraneous char * Changes from review
-
由 dyozie 提交于
-
由 Mark Sliva 提交于
Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io>
-
- 23 3月, 2019 3 次提交
-
-
由 Oliver Albertini 提交于
It's a Bourne Again script, Not a Bourne script. Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NOliver Albertini <oalbertini@pivotal.io> Co-authored-by: NAmil Khanzada <akhanzada@pivotal.io> Co-authored-by: NKris Macoskey <kmacoskey@pivotal.io>
-
由 Oliver Albertini 提交于
The logic hasn't actually changed much (we are still validating the the postgres version and gpdb_src SHA match), but has become clearer and easier to follow: * avoids use of globals * separates assert function into two to have clearer scope separation Co-authored-by: NSoumyadeep Chakraborty <sochakraborty@pivotal.io> Co-authored-by: NAmil Khanzada <akhanzada@pivotal.io> Co-authored-by: NOliver Albertini <oalbertini@pivotal.io> Co-authored-by: NKris Macoskey <kmacoskey@pivotal.io> Co-authored-by: NBen Christel <bchristel@pivotal.io>
- 22 3月, 2019 5 次提交
-
-
由 Jialun 提交于
As a kill may be not taken effect at "the database is killed on hosts " immediately, so we double check the cluster and stop database if it is still running. But if kill takes effect after checking, stop_database will raise an exception for gpstop will fail to stop an unstarted cluster. To fix this flaky case, we stop database first and check the database status later. It will raise an exception only when gpstop failed and the cluster is still running.
-
由 Shoaib Lari 提交于
For some areas of the ICW test framework -- isolation2 in particular -- the additional data written to stdout by gprecoverseg's progress increased the load on the system significantly. (Some tests are buffering stdout without bound, for instance.) Additionally, the updates were coming at ten times a second, which is an order of magnitude more than the update interval we get from pg_basebackup itself. To help with this, we have have added a --no-progress flag that suppresses the output of pg_basebackup. We have also changed the pg_basebackup progress update rate to once per second to minimize I/O. The impacted regression/isolation2 tests utilizing gprecoverseg have also been modified to use the --no-progress flag. Co-authored-by: NJamie McAtamney <jmcatamney@pivotal.io> Co-authored-by: NJacob Champion <pchampion@pivotal.io>
-
由 Kalen Krempely 提交于
When -s is present, show pg_basebackup progress sequentially instead of inplace. Useful when writing to a file, or if a tty does not support escape sequences. Defaults to showing the progress inplace.
-
由 Shoaib Lari 提交于
The gprecoverseg utility runs pg_basebackup in parallel on all segments that are being recovered. In this commit, we are logging the progress of each pg_basebackup on its host and displaying them to the user of gprecoverseg. The progress files are deleted upons successful completion of gprecoverseg. Unit tests have also been added. Authored-by: NShoaib Lari <slari@pivotal.io> Co-authored-by: NMark Sliva <msliva@pivotal.io> Co-authored-by: NJacob Champion <pchampion@pivotal.io> Co-authored-by: NEd Espino <edespino@pivotal.io> Co-authored-by: NKalen Krempely <kkrempely@pivotal.io>
-
由 Bhuvnesh Chaudhary 提交于
-
- 21 3月, 2019 2 次提交
-
-
由 Ning Yu 提交于
These files used to be installed to ${prefix}/bin/ directory, but as they are not user documents we should not install them. Reviewed-by: NBradford D. Boyle <bboyle@pivotal.io> Reviewed-by: NBob Bao <bbao@pivotal.io>
-
由 Bradford Boyle 提交于
The fly commands outputted by gen_pipeline needed to be updated for a chance in the naming convention of one of the secrets files used. Co-authored-by: NBradford Boyle <bboyle@pivotal.io> Co-authored-by: NKris Macoskey <kmacoskey@pivotal.io>
-