MogDB 5.0.2

1. Version Description

MogDB 5.0.2 is a patch version of MogDB 5.0.0, which is released on Sep 30 of 2023. It mainly involves some bug fixes based on MogDB 5.0.1.

2. New Features

1. The standby node table-level parallel replay performance has doubled.
2. Support binding variables in PL/SQL anonymous blocks within Java code.
3. Added a query function for the original statement when creating views.
4. Added error prompts when importing data that exceeds the database character encoding character set range.
5. Introduced the PageHack and PageInspect tools as new additions.

3. Fixed Defects

1. Fixed an issue with incorrect saved view definitions preventing direct creation based on the definition.
2. Fixed an issue where entering safe mode erroneously during index creation prevented the use of temporary tables.
3. Fixed an issue where triggers were causing residual autonomous transactions and leading to crashes.
4. Fixed an issue with the pg_get_function_result and pg_get_function_arguments functions providing incorrect results for composite type collection queries.
5. Fixed the lengthy failover process issue after a network card was brought down.
6. Fixed an issue of incorrect table selection in hash joins.
7. Fixed an issue of incorrect cost calculations in nest loops leading to suboptimal query plans.
8. Fixed an issue in stored procedures where the COPY statement did not display row counts correctly.
9. Fixed an issue of incorrect affected row counts returned when using MERGE INTO through ODBC.
10. Fixed an issue where package objects were not displaying the package name in the notice during cascade deletion.
11. Fixed an issue in Dolphin where the DATE_FORMAT function could not obtain the weekday value.
12. Fixed the inconsistency issue between the TO_DAYS function in Dolphin and MySQL.
13. Fixed the inconsistency problem in Dolphin where the FIND_IN_SET function's execution result differed from MySQL.
14. Fixed the error occurring when hints were included in an INSERT ALL statement.
15. Fixed the slow query plan generation problem caused by lengthy elements in an IN clause for index conditions.
16. Fixed the high memory usage issue caused by enabling the enable_sql_bypass parameter.
17. Fixed the error occurring when a constant constant was used as an input parameter for overloaded functions within a package.
18. Fixed the issue where the gs_is_recycle_obj function was not exported in version 3.0 of gs_dump.
19. Fixed the issue in the CONNECT BY functionality where PRIOR could not be followed by an expression.
20. Fixed the issue of a failed physical backup caused by an error in the getppid system function.

4. Behavior Change

Change Item	Before Upgrade	After Upgrade
Installing the dblink plugin requires dependency packages for the environment.	No additional steps are required; you can create extension directly after installing the dblink plugin.	After installing the dblink plugin, you also need to install the libtool package in order to create extension. The installation command is sudo yum install -y libtool-ltdl-devel.