5.0 release upgrade from PG 8.2 to PG 8.3 (2017 time frame) – JSON/JSONB – Full Text Search – Improved XML Type/Functions – UUID Type – Raster PostGIS – Anonymous Code Blocks – PostgreSQL based Analyze Dispatcher refactoring for improved performance and scalability • More accurate query memory accounting internally • Optimizer and zlib memory usage accounting can be improved • Reduce Intra-Transaction • Pivotal R Support for SVM and LDA • Grouping Support and Cross Validation in Elastic Net • Improved Python Language Support • Investigation on Graph Support • Investigation on GPU support • Performance

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. 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 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

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. 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 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

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. 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 6 Documentation VMware, Inc 141 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

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. 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 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

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 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 plan and execute with GPORCA than with the Postgres Planner. GPORCA planning time performance is improved by disabling partition constraint calculations for such queries. Server 32119 Resolves an issue

window aggregate query crashed during execution by improving MemoryContextContains(). 31391 : Improved the default optimization cost model for GPORCA since the exhaustive2 algorithm was causing performance during scan on bitmap index when there was an INSERT operation running in the backend. 10955 : Improved the logging and adjusted log level from INFO to DEBUG for the message We thought we were done ( partition when the filter condition in a query matched more than a single partition. GPORCA has improved its partition selection algorithm for predicates that contain only disjunctions of equal comparisons

plan and execute with GPORCA than with the Postgres Planner. GPORCA planning time performance is improved by disabling partition constraint calculations for such queries. Server 32119 : Resolves an issue window aggregate query crashed during execution by improving MemoryContextContains(). 31391 : Improved the default optimization cost model for GPORCA since the exhaustive2 algorithm was causing performance during scan on bitmap index when there was an INSERT operation running in the backend. 10955 : Improved the logging and adjusted log level from INFO to DEBUG for the message We thought we were done (

plan and execute with GPORCA than with the Postgres Planner. GPORCA planning time performance is improved by disabling partition constraint calculations for such queries. Server 32119 Resolves an issue a window aggregate query crashed during execution by improving MemoryContextContains(). 31391 Improved the default optimization cost model for GPORCA since the exhaustive2 algorithm was causing performance during scan on bitmap index when there was an INSERT operation running in the backend. 10955 Improved the logging and adjusted log level from INFO to DEBUG for the message We thought we were done (

partition when the filter condition in a query matched more than a single partition. GPORCA has improved its partition selection algorithm for predicates that contain only disjunctions of equal comparisons column name) along with other ungrouped targets that referenced the group key. 10961 - Locking : Improved the locking behavior to avoid deadlocks that can occur when creating multiple indexes on an Append-Only column (ts) to compare column data (a timestamp) to a date. GPORCA partition elimination has been improved to support the specified type of query. See Features. 10491 - Postgres Planner : For some queries