This document contains release information about VMware Greenplum Database 6.x releases. For previous versions of the release notes for Greenplum Database, go to VMware Greenplum Database Documentation. For information about Greenplum Database end of life, see VMware Greenplum Database end of life policy.

VMware Greenplum 6 software is available for download from the VMware Greenplum page on VMware Tanzu Network.

VMware Greenplum 6 is based on the open source Greenplum Database project code.

Upgrading Greenplum

See Upgrading to Greenplum 6 to upgrade your existing Greenplum software.

Release 6.24

Release 6.24.2

Release Date: 2023-04-20

VMware Greenplum 6.24.2 is a maintenance release that resolves a single issue present in versions 6.24.0 and 6.24.1:

32834

Resolves a crash that could occur when running ANALYZE on an append-only, column-oriented table that had dropped columns. This problem was introduced in version 6.24.0 by an optimization to ANALYZE that skipped columns that were dropped from AO/CO tables. The optimization was reverted in 6.24.2.

Release 6.24.1

Release Date: 2023-04-20

VMware Greenplum 6.24.1 is a maintenance release that resolves several issues.

Server

32799 : Resolves a memory leak that could occur when restoring data from a backup to a partitioned table.

32779 : Resolves an issue where a PANIC error could occur on the master segment due to a loss of context during memory allocation.

32756 : Resolves an issue where bitmap index creation on heap tables could fail due to out-of-order transaction IDs resulting from sync scans. Sync scans are now disallowed when building bitmap indexes.

32746 : Resolves an issue where too many processes were remaining in the startup phase for an excessive. This, in turn, was due to VACUUM FULL moving blocks of critical system data to an inefficient location, which delayed process startup.

Query Processing

32747 : Resolves a problem where GPORCA would fall back to using the Postgres Planner for any queries that involved a variadic function (for example, for a function of indefinite arity), thereby generating a sub-optimal plan. GPORCA now supports optimizing queries that involve variadic functions.

Release 6.24.0

Release Date: 2023-03-20

VMware Greenplum 6.24.0 is a minor release that includes new and changed features and resolves several issues.

Features

Greenplum Database 6.24.0 includes these new and changed features:

  • Version 6.24.0 introduces new resource groups and query optimizer features that can be enabled using server configuration parameters:

  • gp_resource_group_bypass_catalog_query - when set to true, Greenplum Database’s resource group scheduler bypasses all queries that both read exclusively from system catalogs and contain in their query text pg_catalog schema tables only, in order to prevent the scheduler from blocking these queries.

  • optimizer_discard_redistribute_hashjoin - provides a method to improve Query Optimizer performance when data to be joined exhibits high skewness in the join keys.
  • Greenplum Database now supports the isn extension, which provides support for the international product numbering standards EAN13, UPC, ISBN (books), ISMN (music), and ISSN (serials).
  • Greenplum Databases’s timestamp9 extension now includes support for the timestamp9_ltz and timestamp9_ntz datatypes.
  • Greenplum Database 6.24.0 deprecates the following features: Greenplum MapReduce, PL/Container 3 Beta and GreenplumR client.
  • GPORCA now supports direct dispatch for randomly distributed tables.
  • VMware Greenplum Streaming Server (GPSS) version 1.9.0 is bundled, which includes new features, changes, and bug fixes. Refer to the Greenplum Streaming Server Documentation for more information about this release and for upgrade instructions.
  • Greenplum Database improves pg_upgrade performance when it handles AO auxiliary tables, by copying relfilenodes to the new cluster instead of rebuilding them.
  • Greenplum Database 6.24.0 introduces the tablefunc module, which provides various examples of functions that return tables.

Resolved Issues

Extensions

32666 : Resolves an issue where a column of type timestamp9 could not be used as a distribution key.

32667, 32668 : Resolves an issue where partition elimination was failing on columns of type timestamp9.

Server

N/A : Resolves an issue where — when a mirror segment got promoted and the original primary segment was disconnected but still running — the original primary segment tried to archive a file that had already been archived.

N/A : Changes the level of an autovacuum log message from LOG to DEBUG1.

30755, 32491 : Resolves an issue where pg_dump failed with error unsupported ALTER command for external table when restoring external tables with serial column types. The fix allows pg_upgrade and gpbackup to support serial column types on external tables.

32617 : Introduces a magic number field to the ICProxyPkt packet to prevent external applications from trying to connect to the ic-proxy process and resulting in hung queries.

32758 : Improves performance of the query gpcheckcat uses for determining vpinfo corruption.

14348 : Fixes a memory leak on the master server that occurred when running INSERT or COPY to an append-only partitioned table.

14561 : Fixes a memory leak by removing redundant invocation of mdinit() at the end of the function smgr_init_standard().

15114 : Removes the restriction of the name data type in pg_upgrade.

14962 : Removes the restriction of tables with partitions belonging in a separate schema than the root partition in pg_upgrade.

15096 : Fixes a bug with function execution in entrydb query execution that reported incorrect number of rows.

15087 : Includes an error message when setting statement_mem to a value greater than max_statement_mem.

15152 : Enhances logging for dispatcher liveness checks to provide more descriptive error messages.

15016 : Resolves an issue where the associated metadata tracking rows in pg_stat_last_operation were not being deleted when dropping a schema.

15005 : Resolves an issue where pg_upgrade returned the error decompression information missing if a column was dropped from an AO/CO table.

Query Processing

N/A : Resolves an issue where GPORCA derived an incorrect equality hash join condition for a character column and returned incorrect results because it grouped operator classes belonging to different operator families as equivalent.

32770 : Resolves an issue where a query that produced a Left Anti Semi Join (LASJ) (NOT IN) plan node was gathered and run on the Greenplum Database master host, generating many spill files and ultimately returning an Out of Memory error. GPORCA now ignores the optimizer_penalize_broadcast_threshold configuration parameter setting when a LASJ requires a replicated distribution.

32665 : Resolves an issue where GPORCA generated a suboptimal plan because it did not push down a filter used in a BETWEEN predicate.

14896 : Resolves an issue where the Query Optimizer produced a faulty plan for certain CTE queries during distribution of sequence children. GPORCA now disallows replicated distribution when the required distribution in sequence is a singleton on master, or when it is a non-singleton with replicated disallowed.

Data Flow

N/A : Resolves an issue where an external table custom formatter had no access to the last line of data it was reading due to incorrect handling of an EOF condition.

32587 : Resolves an issue where a gpfdist process exited because another gpfdist process occupied the same port number (one using an IPV4 socket, one using an IPV6 socket).

32708, 14644 : Resolves an issue with a pg_class catalog table inconsistency after analyzing a table with a dropped subclass.

Cluster Management

32694

gpexpand did not replicate the pg_auth_time_constraints, pg_description, or pg_shdescription tables to new segments because those tables were incorrectly designated as belonging only to the Greenplum master segment. The problem was fixed by removing the tables from the master-only tables list.

32650

Resolved a problem where gpcheckperf, when used without the -S option, incorrectly calculated that a system had twice the actual avaialble memory. This could lead to File System Full errors during filesystem checks.

32446

Fixed runtime errors that could occur when running gpcheckperf with the -V flag (very verbose mode). Now, when gpcheckperf runs in very verbose mode, calls to gpssh are made without verbose mode enabled.

11378

gpstop would sometimes fail to stop all postgres PIDs because the method it used to create the full list of PIDs was not reliable. This problem was fixed by using the postmaster PID to get the list of child processes before stopping the postgres server.

Release 6.23

Release 6.23.3

Release Date: 2023-03-03

VMware Greenplum 6.23.3 is a maintenance release that resolves several issues.

Changed Feature

MADlib version 1.21.0 is available. This release includes additional fixes and features as described in the MADlib Release Notes.

Resolved Issues

Extensions

[N/A]

Addresses TarSlip vulnerability when extracting tarballs for Greenplum Package Manager ( gppkg).

Server

[N/A] The maximum value of the gp_resource_group_cpu_priority configuration parameter has been changed from 256 to 50 to prevent system peformance degradation.

[N/A] Resolves an issue where gpbackup was generating the CREATE TABLE ... PARTITION BY command with syntax errors, due to incorrect printing of signed constants.

32276, 32679, 13809

Resolves an issue where Greenplum Database returned errors similar to 58P01: could not open file : No such file or directory: writing block <block_number> of relation <relation_name>`. Greenplum now better tolerates the failure of bad buffer flushing on a temporary table.

32667

Due to a hard-coded search path, Greenplum Database returned the error operator does not exist: timestamp9 pg_catalog.<= timestamp9 during insertion of a timestamp9 type column into a partitioned table. This issue is resolved; Greenplum now uses the opclass to retrieve an operator for a partitioned table.

14982

Resolves an issue where Greenplum Database returned the wrong results when dynamic partition pruning by the Postgres Planner did not consider the operator class of the partition key.

14887

Resolves an issue where Greenplum Database returned incorrect results during direct dispatch when the operator of a filter clause did not belong to operator family of the distribution key. Greenplum no longer uses direct dispatch in this circumstance.

5003

Resolves an issue with pg_dump external partition handling. It also removes the pg_upgrade restriction against external partitions.

14923 Resolves an issue where changing the distribution key of an append-optimized table was causing pg_upgrade to fail.

14883

Resolves an issue where the type encodings for dependent array types were not preserved during an upgrade from Greenplum 5 to Greenplum 6.

9405

Resolves an issue where a partitioned table could not be created during an upgrade from Greenplum 5 to Greenplum 6 if the table used list partitioning by a custom type and the type’s equality operator was not available in the pg_catalog schema, or was not searchable in the session search_path. The software was modified to obtain the correct schema-qualified operator from the PARTITION BY clause during the upgrade process.

6193

Resolves an issue where an AO/CO table could not be copied if a column had been dropped from the table and the table was subsequently run through pg_upgrade as part of an upgrade process, which generated the error ERROR: decompression information missing.

Query Processing

32731

Resolves an issue where GPORCA returned incorrect results when a query included distinct qualified aggregates.

32695

Resolves an issue where GPORCA generated a crash when a subquery had an ORDER BY clause to an outer reference.

32649

Resolves an issue where GPORCA failed to materialize the inner child of a Nested Loop join and caused performance issues.

32683

Resolves an issue where minirepro diagnostic tool did not collect view statistics nor DDL when the query contained an EXPLAIN command.

MADlib

32672

Resolves an issue where the database hung for a period of time due to a spike in startup processes while running a MADlib query.

Cluster Management

14627

Updates incremental recovery to preserve pg_controldata output for target segments in case of a recovery failure.

Greenplum on vSphere

1472

Resolves an issue in the Greenplum High Availability Service where in some scenarios the service would fail to start while Greenplum is running due to a lower process ID.

1473

Resolves an issue with Greenplum Virtual Service not logging information when errors occurred early in the startup process.

1475

Changed the default behavior of the Greenplum High Availability services, so when Greenplum Database is restarted, the HA services will continue to be active. However in order to stop Greenplum Database, you must stop the HA services first, otherwise Greenplum Database is automatically started.

Release 6.23.1

Release Date: 2023-02-09

VMware Greenplum 6.23.1 is a maintenance release that resolves several issues.

Resolved Issues

Server

32673

Fixes slow query performance when performing a SELECT with a LIMIT clause against a table when using the greenplum_fdw module.

32690

Resolves a PANIC condition that could occur after a server upgrade for certain queries that used the NOT IN clause.

32692

Resolves a problem where gp_autostats_mode_in_functions did not operate correctly in some cases where a COPY or CREATE TABLE .. AS operation ran inside a procedure.

32644

Resolves the error, “ERROR: could not find hash function for hash operator,” that could occur with queries having multiple DISTINCT clauses when using the Postgres Planner.

32609, 32561, 32462

Resolved issues where missing WAL records caused errors during incremental recovery.

32583

Resolves an issue where, after server restart, Greenplum Database returned the error could not access status of transaction <tid> because it could not execute any queries that involved distributed snapshots.

14795

Resolved an issue where the archiver did not attempt to restart when it died during postmaster startup.

14769

Changed the definition of the gpexpand.status_detail table (generated during expansion) to be distributed by the table object identifier to more optimally distribute the workload.

14719

Resolved an issue with standby master activation by initiating an asynchronous connection to the walsender.

14679

Updates pg_dump to ensure that the VMware Greenplum Upgrade utility upgrades check constraints.

14576

Resolves a problem where append-only tables that were upgraded from version 5 could show duplicate ctid system column values, and querys that used the indexes of those tables would return incorrect results. The problem was resolved by preserving the gp_fastsequence table during the upgrade process.

14705

Resolves an issue where Greenplum Database returned the error permission denied for schema <name> during a CREATE INDEX operation when the owner of the table was not the current user.

14649

Resolves the error, “ERROR: schema “” does not exist,” that occured when creating a temporary table from a source table if the source table included comments and either the INCLUDING COMMENTS or INCLUDING ALL clauses was specified.

14520

Resolved an issue where Greenplum Database reported incorrect memory lifetime statistics during out-of-memory conditions and in EXPLAIN ANALYZE output.

14206

Resolved a SEGFAULT that could occur when exchanging partitions with a different distribution policy.

13964

Changed an Assert to a FATAL message log to avoid a crash.

13722

Resolved several assertion failures that could occur for queries with certain join types when using the Postgres Planner.

12690

Resolved a problem where, when memory was limited, certain queries could throw an “insufficient memory reserved for statement” error but would not call the necessary hook for VMware Greenplum Command Center to report the problem.

10269

Added the missing INITPLAN clause to the EXECUTE ON options in the help text for CREATE FUNCTION.

8207

Resolved an issue where ALTER TABLE ... SET WITH (reorganize) invoked on an AOCO table removed some of the table’s reloptions in the pg_appendonly catalog. These options are now retained after reorganizing.

Query Processing

14303

Resolved an issue where GPORCA generated a wrong result for a query on a partitioned table when the query evaluated different types of predicates at the same time (for example, date and timestamp).

13958

Removed redundant PartitionSelector insertion for DML operations.

Data Flow

14759

Resolved an internal error that occurred during an INSERT to an append-only table when the RETURNING clause was used to return the ctid system column value. A similar issue was resolved for INSERTs to a table having a trigger that returns the ctid system column value.

Release 6.23.0

Release Date: 2022-12-21

VMware Greenplum 6.23.0 is a minor release that includes new and changed features and resolves several issues.

Features

Greenplum Database 6.23.0 includes these new and changed features:

  • The CREATE TABLE command includes a new storage parameter — analyze_hll_non_part_table — which allows you to force collection of HLL statistics even if the table is not part of a partitioned table.

  • The gpmt gp_log_collector command now takes a new option — -with-gpcc — which collects Greenplum Command Center logs from a variety of locations, including:

  • $GPCC_HOME/logs/*

  • $GPCC_HOME/conf/app.conf
  • $HOME/gpmetrics/* (Greenplum Command Center 6.8.0+ on Greenplum Database 6.x or Greenplum Command Center 4.16.0+ on Greenplum Database 5.x)
  • $MASTER_DATA_DIRECTORY/gpmetrics (Greenplum Command Center 6.7.0- on Greenplum Database 6.x or Greenplum Command Center 4.15.0- on Greenplum Database 5.x)
  • The output of the gppkg -q --all command
  • The gpmt gp_log_collector command now takes a new option — with-gpss — which collects all logs relevant to Greenplum Streaming Server.
  • The CPUSET syntax for reserving CPU cores for a resource group has changed to require separate separate core specifications for the master host and segments hosts. When using CPUSET with CREATE RESOURCE GROUP or ALTER RESOURCE GROUP you must configure cores for the master host first and then segment hosts, using a semicolon to separate the two. For example, CPUSET='1;1-3' configures core 1 for the master host, and cores 1 through 3 for segment hosts.
  • The Greenplum Database cluster management utilities now use version 5.7.0 of the psutil Python library.
  • The embedded Python distribution is updated to version 2.7.18.
  • Greenplum Database 6.23 limits the number of supported CUBE grouping columns to a maximum of 12.
  • Improves analyzedb performance when it operates on a large number of tables.
  • The gpsd and minirepro diagnostic tools now include the number of segments in their command output.
  • The performance of the minirepro diagnostic tool is improved by using the Postgres Planner instead of the Pivotal Query Optimizer during minirepro restore.
  • Backports upstream PostgreSQL pg_dump performance enhancements.
  • Includes pgcrypto module changes to facilitate testing.
  • The license file for the Windows Client and Loader Tools Package is updated with new terms.

  • Greenplum Database 6.23.0 introduces three new modules:

  • ltree, which provides data types for representing labels of data stored in a hierarchical tree-like structure.

  • timestamp9, which provides an efficient nanosecond-precision timestamp data type.
  • uuid-ossp, which provides functions to generate universally unique identifiers (UUIDs).

  • Version 6.23.0 introduces the following new server configuration parameters:

  • gp_print_create_gang_time - directs Greenplum Database to log additional information about worker process (gang) creation during query execution.

  • gp_max_parallel_cursors - limits the number of active parallel retrieve cursors allowed on a Greenplum Database cluster.
  • optimizer_skew_factor - provides a method to configure GPORCA for skew-aware join costing.

  • The diskquota module was updated to version 2.1, which includes these changes:

  • The 10 database limit is removed, diskquota can now monitor up to 50 databases.

  • The default value of diskquota.max_active_tables is changed to 300 * 1024 to reduce default memory usage.
  • diskquota adds a new configuration parameter, diskquota.max_workers, that you can set to specify the maximum number of diskquota worker processes that may be running at one time.
  • diskquota also adds the diskquota.max_table_segments configuration parameter. You can set this parameter to specify the maximum number of table shards supported by diskquota in the Greenplum Database cluster, which gates the number of tables that it can support.

Refer to the diskquota module documentation for installation and upgrade instructions.

Resolved Issues

Server

32596 : Resolved an issue where Greenplum Database dereferenced a null pointer and PANICed during execution of a query that included record-type parameters.

32567 : Resolved an issue where a query could not be terminated with pg_terminate_backend() because Greenplum Database polled an invalid (-1) file descriptor. Greenplum now removes invalid file descriptors from the polling list.

32557 : Resolved an issue where Greenplum Database returned the error correlated subquery with skip-level correlations is not supported when it executed a query (that ran successfully in a previous version of Greenplum) that included a single-level correlated subquery.

32502 : Added additional logging code for resource queue events.

14465 : Resolved an issue where Greenplum Database returned the error no pre-assigned OID for relation ... when an index was created with a WHERE clause that invoked a function.

32573 : Resolved an issue where Greenplum Database was throwing a “PANIC”,”XX000”,”Unexpected internal error Master process received signal SIGSEGV” error due to incorrect handling of errors in the explain analyze phase of execution.

14510

Resolved a problem where tables created using the WITH (appendonly, orientation=column) had no entries in pg_attribute_encoding, resulting in a table that could not be queried.

14446

Resolved a problem where GRANT and REVOKE statements that involved both partitioned and non-partitioned tables applied their changes only to partitioned tables, with no error or indication that non-partitioned tables were ignored. The code was modified to ensure that such statements are applied to both partitioned and non-partitioned tables.

122

Resolved problem where pg_dumpall, used by the VMware Greenplum upgrade utility, did not correctly dump tablespaces in VMware Greenplum version 5.x databases.

121

Resolved a problem where upgrade could fail with a pg_upgrade error similar to: could not open Append-Only segment file ""base/16410/20863.1665"": No such file or directory"

n/a

Resolved a problem that could cause the error, ERROR: external table <table> command ended with SHELL TERMINATED by signal SIGPIPE (13), with external table queries executed on the master segment when all tuples were not retrieved from a table scan. The problem was fixed by ensuring that squelching mechanics are applied after a SIGPIPE for queries that excecute on the master node, as they are applied for queries executed on segment nodes.

Query Processing

32481 : Resolved an issue where Greenplum Database cancelled a query due to high virtual memory usage when object identifier duplication caused GPORCA to fall back to the Postgres Planner. GPORCA can now handle object identifiers that are not unique across the system.

32453

Resolves an issue where GPORCA failed to produce a plan when the query involved an update on a partitioned table by removing an unused DML column.

32291

Resolves an issue where GPORCA generated a poor plan because it did not identify operation skew. GPORCA introduces the new optimizer_skew_factor server configuration parameter that you can use to enable skew-aware join costing.

14155 : Resolves an issue where a query failed with the error data is corrupt because GPORCA used an incorrect hashing function when it translated a constant value for a text-type domain.

N/A : Resolves an issue where a query that included a DynamicSeqScan with a subplan failed with the error Unexpected internal error.

Cluster Management

32190 : Resolved an issue where gprecoverseg failed to detect than an instance of pg_basebackup was already running, which led to the corruption of the data directory and a PANIC error.

Extensions

N/A : Resolved an issue where diskquota failed to launch new background workers before a slots used by a previous worker was freed. Also changed the logging level for background worker events to less verbose (from INFO to DEBUG1).

N/A : Resolved an issue where, when running pg_basebackup, the last WAL segment file could have a checksum mismatch across the primary and mirror segments.

Other

14530 : Resolved an issue with the open source distribution of Greenplum Database where the installation package was missing required Python libraries.

Release 6.22

Release 6.22.2

Release Date: 2022-11-18

VMware Greenplum 6.22.2 is a maintenance release that resolves several issues.

Resolved Issues

Server

N/A

Resolved an issue where treating non-plan nodes as plan nodes was causing memory corruption and PANIC errors.

N/A

Resolved an issue where a CREATE INDEX command on an AO/CO table would hang if there was a pre-existing read-only transaction accessing the same table.

N/A

Resolved an issue where a key internal process was crashing when theree were too many simultaneous connections to the database.

N/A

Resolved an issue where memory corruption occurred after a VACUUM command due to an internal data structure not being correctly initialized.

N/A

Resolved an issue where DELETE FROM queries on AO/CO auxiliary tables were erroring out.

N/A

Resolved an issue with pg_dump where, during gpcopy operations, external leaf tables were copied as heap tables instead of external tables.

32523, 32314

Resolved an issue where Greenplum Database might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown.

32367

Resolved an issue where Greenplum Database was consuming high amounts of memory when processing column oriented tables that had high numbers of partitions.

32367, 14122

Resolved memory leaks related to dynamic bitmap scan on column-oriented tables.

32495

Resolved a performance issue that occured when Greenplum Database planned a query that included a subselect containing a GROUP BY clause (as distinct).

32491

Resolved an issue where pg_upgrade failed when it restored an external table that had a dropped column(s).

32455

Resolved an issue where a PANIC error occurred after an attempt to split a partition into a new partition and a default partition on a table that did not have a default partition.

32458

Resolved an issue where running an internal function on a partition table caused the master Greenplum Database instance to crash.

32500

Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC","XX000","Unexpected internal error: Master process received signal SIGSEGV occurred after executing a query that included an unsupported feature.

14177

Resolved an issue where a snapshot could not be imported because the timestamp was missing, affecting snapshot visibility.

14107 : Resolved an issue where Greenplum Database returned the error operator 37 is not a valid ordering operator because it incorrectly generated a sort operator and equality operator when the types of left and right operand differed.

14003 : Resolved a compile warning by replacing a strncpy() call with memcpy().

Query Processing

32525

Resolved a problem where GPORCA would fall back to the planner for queries having an intersection of bit values if one of the bit vectors returned a size of 0. GPORCA now correctly removes the empty vector and produces a correct query plan.

32505

Resolved an issue where GPORCA did not generate a performant plan when the query included an N-ary join with only inner joins, and the predicate was false.

32480

Resolved a crash that could occur during query planning for certain UNION queries if the output column for the first child of the UNION was dropped in the projection, making statistics for the column unavailable. The problem was resolved by ensuring that none of the project eleents are dropped.

32450

Resolved a problem where GPORCA failed to do direct dispatch when filtering gp_segment_id on conjunction constraints.

32291

GPORCA now produces a more performant query plan for queries where it can propagate a predicate from scalar ANY subquery to the outer relation.

14297

Fixed a regression in PostGIS compatibility that caused an exception if the TVF constant value was NULL. GPORCA now correctly falls back to the planner in this case.

14273

Resolved an issue where GPORCA could crash when a query involved dynamic partition elimination with a dynamic partial scan.

14246

Resolved a dependency issue that occurred when minirepo was run on a query that accessed a materialized view.

Data Flow

32536

Resolved a pgbouncer problem where admin users logging into the pgbouncer database were logged in as the pgbouncer user instead of as the configured admin_user.

Release 6.22.1

Release Date: 2022-10-07

VMware Greenplum 6.22.1 is a maintenance release that resolves several issues.

Resolved Issues

Server

32314-1

Resolved a problem where queries could hang while using an interconnect proxy if network issues occurred during common TCP interconnect teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver’s connections.

32314-2

Resolved a problem where logs from ic_proxy did not consider the current setting of the gp_log_interconnect configuration parameter. The parameter value is now taken into consideration in the ic_proxy logging mechanism.

14189

Resolves an issue where a mirror failed to start archiving WAL after it was promoted when the mirror was configured with archive_mode=on.

14000

Resolves an issue where Greenplum Database wasted resources when it examined plan nodes that belong to other slices and initialized unnecessary structures. Greenplum now eliminates alien nodes before execution for entry db.

13997

The psql command \d+ now shows correct index information for append-only auxiliary tables.

13739

Resolves an issue where Greenplum Database returned a wrong result or silently errored out when a subplan contained a SharedScan and the subplan’s parent Plan included motion, by fixing cross-slice interaction detection for subplans.

11948

Resolved a crash that could occur because Greenplum incorrectly allowed REINDEX TABLE on a partitioned table from within a PL/SQL function. Because REINDEX TABLE on partitioned table expands the table and starts a new transaction to reindex each table, the operation cannot be rolled back and may crash if called within PL/SQL. The code was modified to prevent this operation from running inside of a function.

Query Processing

32467

Resolved a query failure that could occur if a predicate with a set-returning function was pushed down in cases where the context could not accept a set. The existing logic was updated to ensure that such predicates are not pushed down.

32465

Resolves an issue where Greenplum Database consumed a large amount of memory when GPORCA planned certain queries that generated a dynamic bitmap scan.

32307

Resolved a problem where GPORCA generated poor query plans because it did not permit aggregate functions from running on replicated slices. This meant that results were always broadcasted or gathered on a single segment in order to ensure consistency and correct results. The code was modified to ensure that commonly-used aggregate functions which are not sensitive to the order of data (such as sum, avg, count, min, and max) are safely executed. For cases where aggregate functions are sensitive to the order of data (such as array_agg and custom user-created functions) this optimization is avoided.

32233

Addressed a performance problem where outer join operations performed unnecessary data redistribution to create a hash distribution specification from the inner relation. The code was modified to derive a combined hash specification for outer join operations from both relations.

Cluster Management

32289

Resolves an issue where gpcheckcat incorrectly flagged default privilege objects as having missing dependencies.

11105

Resolved a problem where gpactivatestandby promotion could fail because the process did not wait long enough for the walreceiver process to shut down. The problem was fixed by synchronizing the standby promotion timeout value with the mirror promotion timeout value.

Release 6.22.0

Release Date: 2022-09-09

VMware Greenplum 6.22.0 is a minor release that includes new and changed features and resolves several issues.

Features

Greenplum Database 6.22.0 includes these new and changed features:

  • Greenplum Database now includes a plugin that allows you to monitor Greenplum Text clusters via Greenplum Command Center. For more information, see Monitoring Greenplum Text.
  • A new extension, plpython3u, is provided to support developing Python 3.9 functions with PL/Python. See PL/Python Language. An additional Data Science Package for Python is provided to install common Python 3.9 modules for developing plypython3u functions. See Data Science Package for Python.
  • The Data Science Package for Python 2.7 was updated to add the regex package. The package versions for lxml, nltk, tenserflow, tenserflow-gpu, and keras were updated to address CVEs.
  • pg_dump performance was improved to reduce the time required to dump database schemas during the upgrade process. This especially benefits clusters that have a large number of append-optimized tables.
  • Greenplum Database now includes a view — gp_suboverflowed_backend — created by the new extension gp_subtransaction_overflow-- to help users query for suboverflowed backends. Users can use segment id and process id information reported in the view to terminate the offending backends, thereby preventing degradation of performance. For more information, see Monitoring a Greenplum System.
  • Greenplum Database now includes an extension — gp_pitr — to support implementing Point-in-Time Recovery for Greenplum Database 6X. gp_pitr creates a new view — gp_stat_archiver — and two new internally used user-defined functions. For more information, see Additional Supplied Modules.
  • The pgcrypto extension was updated to support FIPS encryption via the pgcrypto.fips configuration parameter. See Configuring FIPS Encryption in the pgcrypto documentation.
  • The diskquota module was updated to version 2.0.1, and introduces a change to logging behavior. Now, if the diskquota module is enabled in a database that has existing data but you do not run the diskquota.init_table_size_table() function, a single error message is logged when the Greenplum cluster starts up. In earlier versions of diskquota, the error message was logged repeatedly (approximately every 2 seconds) and could flood the log monitor system with the same error.
  • Greenplum Database introduces a new server configuration parameter, optimizer_enable_replicated_table, that you can use to control GPORCA’s behavior when it encounters DML operations on replicated tables. By default, GPORCA attempts to plan and execute operations on replicated tables.
  • Greenplum Streaming Server (GPSS) version 1.8.0 is included, which includes new features, changes, and bug fixes. Refer to the Greenplum Streaming Server Documentation for more information about this release and for upgrade instructions.
  • The s3 protocol now supports obtaining S3 authentication credentials from the default AWS credential file, ~/.aws/credentials.
  • gpfdist now supports reading and writing files compressed with the Zstandard compression algorithm.
  • The file protocol now supports reading files compressed with the Zstandard compression algorithm.
  • Greenplum Database 6.22.0 introduces a new module, ip4r, that provides data types for operations on IPv4 and IPv6 IP addresses.
  • Greenplum Database 6.22.0 introduces a new module, postgresql-hll, that provides HyperLogLog data types for PostgreSQL and Greenplum Database.
  • The gp_percentile_agg module has been updated fix a bug and to generate more performant plans for ordered-set aggregates with skewed data. If you are currently using this module, you must upgrade the module after you upgrade Greenplum Database.
  • Greenplum Database 6.22.0 adds the f_smgr public interface for storage operations.
  • The performance of gpexpand computation of table size has been improved.
  • The PgBouncer distributed with Greenplum Database 6.22.0 adds support for native LDAP authentication between the psql client and the pgbouncer process. Refer to Configuring LDAP-based Authentication for PgBouncer for configuration information.
  • Greenplum Database supports configuring the ldapsearchfilter attribute in pg_hba.conf. You can optionally use this attribute to provide a search filter to use when doing search+bind authentication. See LDAP Authentication.
  • Greenplum Database improves pg_dump performance by gathering AO metadata in a single query.
  • The VMware Greenplum Connector for Apache NiFi version 1.1.0 is available, which includes a change. Refer to the Greenplum Connector for Apache NiFi Documentation for more information about this release.
  • The gpmt gp_log_collector utility now includes the --with-gpbackup option to collect logs related to backup and restore operations. See gpmt gp_log_collector.
  • The DataDirect ODBC drivers were updated to version 7.1.6+7.16.445 to include the latest fixes and to no longer require acceptance of a separate licensing agreement. If you have installed a DataDirect ODBC driver version 7.1.6+7.16.389 or earlier, see Upgrading DataDirect ODBC Drivers. The new version resolves a compatibility issue with the Greenplum Direct Query Custom .pqx connector and Microsoft’s PowerBI Gateway. Both the ODBC driver and .pqx connector must be upgraded on Desktop and Gateway systems.

Resolved Issues

Server

32398 : Fixes double freeing of a buffer during stream teardown that resulted in a PANIC.

32384 : Resolves an issue where a CTE query that involved several columns caused Greenplum Database to PANIC.

32381 : Resolves Postgres CVE-2022-2625, Extension scripts replace objects not belonging to the extension.

32271 : Resolves an issue where SELECT or other read-only operations resulted in setting hint bits on pages, which generated Full Page Imag

（本文超出站点单文档体积上限，已截断）