VMware Tanzu Greenplum 6.12.1 resolves these issues:

9207 - Server Standby

Fixed a memory overflow condition that could cause a standby node to shut down with the error, "FATAL","XX000","the limit of 500 distributed transactions has been reached (cdbdtxrecovery.c:571)".

11003 - Postgres Planner

Resolved an issue where a query that selected a constant and that specified one or more empty GROUPING SETS returned incorrect results.

30923 - Server Execution, Planner

Resolved a problem where a query could return incorrect results if segments held a NULL value in an empty set.

30946 - Query Optimizer

A query on a table with a btree index ran longer than expected because the Query Optimizer did not perform partition elimination when the query included an index join with both a local and a join predicate. This issue is resolved; the Query Optimizer improves dynamic and static partition elimination when indexes are present.

30993 - Optimizer

Fixed an issue where certain IN queries performed slowly because full table scans were used instead of indexes.

30999 - Cluster Management

Fixes an issue where moving a mirror segment to an alternate host, using gprecoverseg -F, was failing.

31007 - Cluster Management

Fixes an issue where no error was logged or reported when the incremental recovery of a segment using gprecoverseg failed. The logs now include a message similar to: [WARNING]:-Incremental recovery failed for my-segment-name. You must use gprecoverseg -F to recover the segment.

31014 - analyzedb

Fixed a problem where analyzedb could fail if a table was dropped and recreated during the analyzedb operation.

31018 - gpexpand

The redistribute phase of a cluster expansion returned the error ... failed to expand: error ERROR: ... is not a table when it tried to expand a materialized view. This issue is resolved; Greenplum Databae now supports expanding materialized views.

31026 - Metrics Collector

Resolved an issue where Greenplum Command Center version 6.3.0 and 6.3.1 could not show a visual query plan in the query monitor in certain cases.

31057 - Optimizer

When simplifying constraints during preprocessing, GPORCA did not consider the case where a constraint compared a column to an empty array (for example, EXPLAIN SELECT 1 FROM mytable WHERE mytable.mycolumn=ANY('{}');). These types of queries would cause GPORCA to crash. This problem was resolved by ensuring that GPORCA now skips merging a constraint with an empty array.

174906043 - Metrics Collector

Resolved an issue where the Greenplum Command Center could not show metrics for CREATE TABLE AS SELECT … FROM and COPY (SELECT ... FROM ...) TO ... statements.

175050196 - autovacuum

Resolved a fatal error that could occur when the autovacuum daemon performed a VACUUM operation on the template0 database.

175372920 - Resource Groups

Resolved an issue that could cause queries to fail if an earlier DROP RESOURCE GROUP command failed to drop the resource group.

175471857 - Query Dispatcher

Resolved a problem that could cause a transaction to incorrectly use single-phase commit instead of two-phase commit.

275569338 - Query Dispatcher

Resolved a problem that could cause the error, ERROR: unrecognized node type: 2139062143 (copyfuncs.c:6059), when the query dispatcher needed to refresh a materialized view.

Greenplum Database 6.12.0 includes these new and changed features:

• Greenplum now supports using segment hostnames when defining proxy ports with the gp_interconnect_proxy_addresses parameter (previously, IP addresses were required). Note that if a segment instance hostname is bound to a different IP address at runtime, you must execute gpstop -U to re-load the gp_interconnect_proxy_addresses value. See Configuring Proxies for the Greenplum Interconnect.
• Because Greenplum Database does not enforce referential integrity syntax (foreign key constraints), the TRUNCATE command was updated so that it truncates a table referenced in a foreign key constraint, even if the CASCADE option is omitted.
• The Greenplum Database 6.12.0 distribution includes the Greenplum Magic Tool (gpmt), a diagnostics and data collection tool.
• The Greenplum Database 6.12.0 distribution includes the postgres_fdw PostgreSQL contrib module. Refer to the postgres_fdw module documentation for more information.

VMware Tanzu Greenplum 6.12.0 resolves these issues:

174311661 - Query Execution

When executing a long query that contained multi-byte characters, Greenplum could incorrectly truncate the query string (removing multi-byte characters) and, if log_min_duration_statement was set to 0, could subsequent write an invalid symbol to segment logs. This behavior could cause errors in gp_toolkit and Command Center. This problem has been resolved.

173190958 - Transactions

In some cases, a Greenplum Database master reset generated one or more orphaned prepared transactions. This issue is resolved; Greenplum now periodically checks for, and aborts, these transactions.

171249005 - Transactions

Resolves an issue where Greenplum Database generated a PANIC when it exhausted retry attempts to abort prepared transactions.

30992 - Transactions

In some cases, Greenplum Database generated a PANIC after reboot due to a race condition between a checkpoint and xlog COMMIT PREPARE recording. When Greenplum encountered an orphaned prepared transaction that was committed after the xlog was recorded, it returned the error message: cannot abort transaction transaction_number, it was already committed. This issue is resolved.

30970 - Query Optimizer

In some cases, Greenplum Database crashed when the Query Optimizer attempted to generate an index scan from a predicate that contained a subquery. This issue is resolved; the Query Optimizer now disallows such plans.

30962 - Query Optimizer

The second SELECT on an external table within a transaction returned zero records because the Query Optimizer did not generate a unique scan number to differentiate the two queries to the external table. This issue is resolved.

30960 - Query Optimizer

Resolves an issue where the Query Optimizer entered an infinite loop when it merged statistics buckets for double values in UNION and UNION ALL queries due to an incorrect comparison of bucket boundary values with a small Epsilon.

30980 - diskquota Module

Resolved an issue that caused master and mirror segments to display the warning, Share memory is not enough for active tables, when TRUNCATE and CREATE TABLE statements were executed.

30942 - Postgres Planner

In some cases, the Postgres Planner crashed or produced incorrect results when the HAVING clause of a query included a subquery, and one or more columns referenced in the subquery were not also specified in the GROUP BY column set. This issue is resolved.

10813 - Postgres Planner

Resolved an issue that could cause the Query Dispatcher to crash when creating a query plan for a subquery that has GROUPING SETS.

10794 - Resource Groups

Resolves an issue where the result of a query on pg_resgroup_get_status(NULL:oid) could not be saved to a table.

10376 - Query Execution

Resolved an issue where executing CREATE UNIQUE INDEX on a table partition would implicitly change the partition's distribution key.

425 - gpbackup

When inserting into a table that is distributed by a bpchar and using the legacy bpchar hash operator, rows always used jump consistent hashing instead of legacy (modulo) hashing. This mismatch would cause gprestore operations to fail for when restoring Greenplum 4.x/5.x data into Greenplum 6.x. The problem occurred because a required hashing function ID was missing from a check function that determined if an attribute used legacy hashing. Greenplum 6.12 resolves this issue by adding the required hashing function ID in the check function.

See Upgrading from an Earlier Greenplum 6 Release to upgrade your existing Greenplum 6.x software to Greenplum 6.12.0.