Release notes of Greengage DB 6.29.0

New features

Implemented tracking and deleting orphaned files. For more implementation details, see Deleting orphaned files. You can manage whether to apply the new approach to processing orphaned files (described in that article) using the gp_track_pending_delete GUC. The default parameter value is on, which means using the new approach. Note that the gp_track_pending_delete parameter value can only be modified by editing the postgresql.conf file on all segments using the gpconfig utility; and you need to restart Greengage DB to apply your changes.

Remember that installation of Greengage DB 6.29.0 does not allow you to delete already existing orphaned files, but it will prevent them from being produced in the future

Backported the Dynamic Shared Areas (DSA) module from PostgreSQL

Bug fixes

Fixed the update lost during inplace updates

Backported PostgreSQL fixes for archive_mode = on/always

Fixed gp_default_storage_options that affected reorganization of heap tables

Prevented usage of free memory in the flatten_join_alias_var_optimizer function

Fixed pushdown of the HAVING clauses in ORCA

Disabled decorrelation for COUNT() with no grouping columns

On the object creation step, added protection from dropping referenced objects

Fixed gp_check_functions to handle custom tablespaces correctly

Started to use the correct way to detect inner queries in SPI

Fixed an issue that caused the COPY command to hang while working with column-oriented tables where all columns had been dropped

Threw out fault injector code blocks for release builds

Fixed lost executor error messages after query cancellation

Disabled storing plain types in short varlena format

Added MemoryAccounting_Reset to GDD

Disabled materialization of a sorted internal path in MERGE JOIN

Added a check for scalar subplans in the ORCA’s translator Expr → DXL

Greengage DB 6.29.0 product release