MogDB 5.0.10

1. Version Description

MogDB 5.0.10 is a patch version of MogDB 5.0.0, released on 2024-12-31. It adds a new feature and fixes some defects based on MogDB 5.0.9, with the following details:

2. New Features

2.1 Anonymous Sql Cache Support

When users execute anonymous plan caching through libpq, calling PQprepare and PQexec anonymously multiple times to execute the same SQL will trigger multiple parsing, resulting in performance degradation.

This feature improves the efficiency of this scenario by supporting caching of these anonymous plans to a certain extent, avoiding duplicate parsing caused by multiple user calls.

Related Page: Anonymous Sql Cache Support

2.2 Compatibility Enhancement

In the 'create table as' statement, the numerical constants in the table are set to' int 'by default in MogDB, while in Oracle, they are set to' number 'by default. MogDB has added support for converting them to' number 'through the GUC parameter' enable_int_to_numeric '. Behavior is consistent with Oracle.

2.3 Copy To Logic Enhancement

In the old version of MogDB, when copying, only the arbitrary precision value itself is output, and 0 is not automatically filled on the left side. This feature is targeted for decimal types in CSV scenarios in the copy to logic, adding relevant logic for filling 0 and+, and automatically filling 0 on the left side of arbitrary precision values.

2.4 Logical Replication Supports DDL Operation Extension

On the basis of supporting DDL operations in MogDB 5.0.8 logical replication, some DDL parsing has been added to further enhance the dual track parallel capability of MogDB and heterogeneous databases.

Related Page: Logical Decoding Support For DDL

2.5 Optimization Of Ustore Hotspot Update Page

Frequent updates to hot pages can lead to a large number of historical versions and the possibility of TD chains being repeatedly reused. This version solves the problem of query latency degradation at multiple levels on frequently updated hotspot pages.

Related Page: In Place Update Storage Engine Ustore

3. Defect Fixes

1. [9782] Fixed an error when multiple tables have the same column in B mode and the alias and the name after 'order by' have inconsistent capitalization.

2. [9265] Fixed the issue of gs_debackup remote backup failure.

3. [5505] Fixed the issue where MogDB did not replay the xlog index related logs before upgrading from MogDB 3.0.x to MogDB 5.0.x and later versions, and replaying the index logs after upgrading would result in upgrade errors.

4. [9800] Fixed the issue where modifying the return type of a custom function in A-style would result in incorrect query results for views referencing this function.

5. [9348] Fixed the issue of VIP automatically pulled up by CM and the probability of packet loss during remote access.

6. [6780] Fixed the issue where the behavior of the record constructor function (record_in) in handling empty string attributes was inconsistent with that of A

7. [4884] Fixed the issue of incorrect data change records captured by wal2json after partition table exchange.

8. [9722] Fixed an issue where there were a large number of database objects (tables) with default values in each column, and the additional memory used by the adbin_on_update field was not actively released during the database syscache cleanup process, resulting in a memory leak.

9. [9688] Fixed the database crash issue caused by the min/max optimization triggered by the database optimizer in B mode when the SQL mode full group was closed.

10. [9675] Fixed the issue where frequent calls to the decoding function may result in database crashes when using logic decoding and sequences.

11. [9451] Fixed the issue where the force index did not take effect when there were too many in() conditions in the where clause of the select clause in B mode.

12. [9673] Fixed the issue of memory expansion caused by frequent use of union all.

13. [9823] Fixed the issue of memory accumulation when using copy from.

14. [9794] Fixed the issue of database downtime caused by the probability of using index scan in stored procedures.