MogDB 5.0.7

1. Version Description

MogDB 5.0.7 is a patch version of MogDB 5.0.0, released on 2024-05-30. It addresses some defects on top of MogDB 5.0.6, with details as follows:

2. Defect Fixes

1. [5004] Fixed an issue where the Cluster Manager (CM) experienced abnormal functionality when adding two VIPs in a single network segment scenario.
2. [5002] Fixed an issue where changes in the support for type conversion of select decode led to errors in certain scenarios.
3. [4120] Fixed a probabilistic core dump issue that occurred with the alter table add column after statement.
4. [4988] Fixed an abnormal query status issue that persisted when continuously checking the value of the protect_standby parameter after setting it to on with the reload command.
5. [5998] Fixed a failure in the CM to automatically mount the VIP in a one-primary, one-standby scenario.
6. [4999] Fixed an issue where the "tidrangescan" plugin was not automatically created when upgrading from a lower version of MogDB 5.0 to MogDB 5.0.6.
7. [5006] Fixed an error that occurred when setting user passwords with parallel export enabled in gs_dump.
8. [5007] Fixed a failure in the recovery operation based on incremental backups with gs_probackup.
9. [5076] Fixed an error that occurred when using gs_dump to export a database in the B library scenario and then importing it with gs_restore.
10. [5125] Fixed a core dump issue that occurred when restoring a full backup with gs_probackup and specifying a non-existent ID with the -i option.
11. [5152] Fixed an error that occurred when the rewrite_rule was set to column_pruner and the window function included a partition clause.
12. [4508] Fixed a probabilistic core issue caused by concurrent DDL package operations.
13. [5003] Fixed an error that occurred when executing SQL statements involving at least 15 table joins with an Append join operator, reporting the issue "bitmapset has multiple members".
14. [5217] Fixed a probabilistic data outage issue caused by modifying table fields with ALTER TABLE … FIRST/AFTER.
15. [5151] Fixed a memory overflow issue that occurred when there were 128 users or a multiple of 128 users, and the 128th user was deleted while simultaneously querying the gs_sql_count system view.