Pivotal Greenplum 6.9.1 resolves these issues:

n/a

The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect Release Notes for additional information.

30750

The ANALYZE code did not exclude external tables (which cannot be analyzed) if an external table was part of a table partition hierarchy. This would result in the failure ERROR: unsupported table type when performing partitioned table operations that use ANALYZE, such as ALTER TABLE … EXCHANGE PARTITION. The problem was resolved by updating the ANALYZE code to correctly exclude these external tables.

Greenplum Database 6.9.0 includes these new and changed features:

• Greenplum Streaming Server (GPSS) version 1.4.0 is included, which introduces many new and changed features and bug fixes. Refer to the GPSS Release Notes for more information on release content and to access the GPSS documentation.
  Note: If you have previously used GPSS in your Greenplum 6.x installation, you are required to perform upgrade actions as described in Upgrading the Streaming Server.
• PXF version 5.13.0 is included, the first PXF release to also provide a separate download package that enables you to install PXF in a file system location outside of the Greenplum install directory. Refer to the PXF Release Notes for more information on release content and supported platforms, and to access the PXF documentation.

Pivotal Greenplum 6.9.0 resolves these issues:

30630 - Segment Mirroring

In some cases during a failover of a segment instance, Greenplum Database returned the FATAL error requested WAL segment WAL_seg_ID has already been removed. Greenplum Database WAL replication incorrectly removed segment files before they were processed during failover. This issue is resolved.

10216 - ALTER TABLE, ALTER DOMAIN

In some cases, heap table data is lost when performing concurrent ALTER TABLE or ALTER DOMAIN commands where one command alters a table column and the other rewrites or redistributes the table data. For example, performing concurrent ALTER TABLE commands where one command changes a column data type from int to text might cause data loss. This issue might also occur when altering a table column during the data distribution phase of a Greenplum system expansion. Greenplum Database did not correctly capture the current state of the table during command execution. This issue is resolved.

10224 - ALTER TABLE

For a leaf partition of a partitioned table, ALTER TABLE allowed the distribution policy to be changed to REPLICATED. This is resolved. ALTER TABLE no longer allows the change.

30647 - Postgres Planner

Some queries that performed multistage aggregation returned results in the incorrect order. For example, some queries that perform a COUNT in the select list and also contain a GROUP BY clause returned results in the incorrect order. This issue is resolved.

10013 - Postgres Planner

In some cases, Greenplum Database generated a PANIC when it encountered a lateral subquery that included a LIMIT 1 or GROUP BY clause. Greenplum 6.9 resolves this issue by forcing the gathering and materialization of any relation containing a GROUP BY or LIMIT clause.

10315 Postgres Planner

For some queries that perform a FULL JOIN using a subselect that contains a COALESCE function, Greenplum Database returned "ERROR: could not find hash distribution key expressions in target list". This issue is resolved.

8919 - MPP, Query Execution

Greenplum Database did not properly handle concurrent updating operations to a table when one of the operations moved a table distribution key to another segment instance. Now when a table distribution key is moved to another segment instance, a concurrent updating operation returns an error.

173243811 - Resource Groups

When resource groups are enabled and a user attempted to move a running query from one resource group to a resource group configured using the memory_limit=0 with the pg_resgroup_move_query() function, Greenplum Database returned the error ERROR: group <group_ID> doesn't have enough memory on master. This issue is resolved.

172931886 - Transaction System

Greenplum 6.9 resolves an issue where restarting a primary could lead to a segment process hang when there were prepared, but not yet committed or aborted, transactions in progress at the time of shutdown.

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