Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Release notes:
https://gpdb.docs.pivotal.io/560/relnotes/GPDB_561_README.html#topic_irl_p5n_scb
Note: We will not support the experimental features offered in this version.
PL/Container is installed as a Greenplum Database extension. PL/Container 1.1 is installed by gppkg as a Greenplum Database extension, while PL/Container 1.0 extension is installed as a Greenplum Database language. Upgrading to PL/Container 1.1 from 1.0 requires uninstalling PL/Container 1.0.
In the PL/Container configuration file, the cpu_share attribute of a settings attribute is a relative weighting of CPU usage compared to other containers. For example, a container with a cpu_share of 2048 is allocated double the CPU slice time compared with container with the default value of 1024.
For information about the PL/Container extension in Greenplum Database including upgrading to PL/Container 1.1, see PL/Container Language Extension.
The Greenplum Database server configuration parameter gp_ignore_error_table controls Greenplum Database behavior when the INTO ERROR TABLE clause is specified in a CREATE EXTERNAL TABLE or COPY command. The INTO ERROR TABLE clause was removed in Greenplum Database 5.
The default value is false, Greenplum Database returns an error if the INTO ERROR TABLEclause is specified in a command.
If the value is true, Greenplum Database ignores the clause, issues a warning, and executes the command and logs information about data rows with formatting errors. In Greenplum Database 5.x, you access the error log information with built-in SQL functions. See the CREATE EXTERNAL TABLE or COPY command.
You can set this value to true to avoid the Greenplum Database 5 error when you run applications that execute CREATE EXTERNAL TABLE or COPY commands that include the Greenplum Database 4.3.x INTO ERROR TABLE clause.
| Value Range | Default | Set Classifications |
|---|---|---|
| Boolean | false |
master
system reload |
For information about Greenplum Database server configuration parameters, see Server Configuration Parameters.
Greenplum Database 5.6 provides integration with the new Pivotal Greenplum-Informatica Connector (experimental). The Pivotal Greenplum-Informatica Connector supports high speed data transfer from an Informatica PowerCenter cluster to a Pivotal Greenplum Database cluster for batch and streaming ETL operations.
Greenplum Database 5.6 introduces the Greenplum Streaming Server (GPSS) component, which manages all communication between the Informatica PowerCenter node and the Pivotal Greenplum Database cluster. See the Pivotal Greenplum-Informatica Connector (Experimental) Documentation.
The Greenplum Metrics Collection Extension has been added to this release. This extension is a prerequisite for an upcoming Pivotal Greenplum Command Center release on Red Hat and CentOS platforms, and is not yet enabled.
The extension is installed in the$GPHOME/share/postgresql/extension/metrics_collection directory, and its library files are installed in the $GPHOME/lib/postgresql directory.
The server configuration parameter shared_preload_libraries in the master and segment postgresql.conf files is updated to include the name of the extension's shared library, metrics_collection.so.
No actual changes to the ADS code need to be made other than to test with the latest version and drivers.
Thanks Tom, for correcting Greenplum version.
We have already done end to end testing for ticket 15570 where we did regression test for Greenplum 5.0 and 4.3 both.
So we are good to go for marking this ticket as verified.
Thanks Tom, for correcting Greenplum version.
We have already done end to end testing for ticket 15570 where we did regression test for Greenplum 5.0 and 4.3 both.
So we are good to go for marking this ticket as verified.
Hi Juhi,
Sure. Please mark it verified.
Thanks, Tom
Hi Juhi,
Sure. Please mark it verified.
Thanks, Tom
Issue #15539 |
| Verified |
| Fixed |
| Resolved |
Completion |
| Due Mar 30, 2018 |
| Fixed Build ADS19.5.0-dev-11 |
| No time estimate |
No actual changes to the ADS code need to be made other than to test with the latest version and drivers.