Greenplum Database 4.2.6 runs on the following platforms:
• Red Hat Enterprise Linux 64-bit 5.5, 5.6, 5.7, 6.1, and 6.2
• SUSE Linux Enterprise Server 64-bit 10 SP4, 11 SP1
• Solaris x86 64-bit v10 U7, U8, U9, U10
• Oracle Unbreakable Linux 64-bit 5.5
• CentOS 64-bit 5.5, 5.6, 5.7, 6.1, and 6.2
Greenplum Database 4.2.6 supports Data Domain Boost on Red Hat Enterprise Linux.
Greenplum Database 4.2.6 supports Data Domain Boost SDK version 220.127.116.11 with DDOS 18.104.22.168, 5.1 and 5.2.
GPDB 22.214.171.124 was certified against the following DCA versions:
• DCA v1 - ISO_VERSION="126.96.36.199"
• DCA v2 - ISO_VERSION="188.8.131.52"
Note: For the most recent server platform support information for Greenplum Database, check the EMC Support Matrix (ESM).
To access the ESM, go to the Support Zone home page and click the link E-Lab Interoperability Navigator.
In the E-Lab Interoperability Navigator, search for Greenplum Database and add one or more search results to the search cart. Click Get Results to display links to
EMC Support Statements.
Greenplum Database 184.108.40.206 includes enhancements in these areas:
• Ability To View Long Query Text Strings from pg_stat_activity View
• Server Configuration Parameters
Ability To View Long Query Text Strings from pg_stat_activity View
The maximum length of the query text string in the current_query column of the system catalog view pg_stat_activity can be controlled by the Greenplum Database
configuration parameter pgstat_track_activity_query_size. The minimum length is 1024 characters. For information about the Greenplum Database configuration parameter and view, see the Greenplum Database Reference Guide.
Server Configuration Parameters
• New Parameter
• Changed Parameter
New Parameter :
pgstat_track_activity_query_size : Sets the maximum length limit for the query text stored in the current_query column of the system catalog view pg_stat_activity. The minimum length is 1024 characters.
Default value: 1024
gp_resqueue_memory_policy : Enables Greenplum memory management features. In Greenplum Database 4.2 and later, the distribution algorithm
eager_free, takes advantage of the fact that not all operators execute at the same time. The query plan is divided into stages and Greenplum
Database eagerly frees memory allocated to a previous stage at the end of that stage’s execution, then allocates the eagerly freed memory to the new
stage. When set to none, memory management is the same as in Greenplum Database releases prior to 4.1. When set to auto, query memory usage is
controlled by statement_mem and resource queue memory limits.