AWS AmazonRDS documentation change
Summary
Updated Aurora MySQL 8.4.7 release notes with improved wording and clarity. Changes include grammatical fixes, clearer explanations of upgrade paths, and more precise descriptions of bug fixes related to instance restarts, switchover operations, query ordering, DDL operations, and parallel query processing.
Security assessment
The changes are documentation improvements without explicit security context. Bug fixes described (e.g., preventing repeated writer restarts, fixing incorrect query results) address stability and correctness issues but show no evidence of patching vulnerabilities that could be exploited by attackers. No CVEs, security advisories, or vulnerability mitigation language is present.
Diff
diff --git a/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.847.md b/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.847.md index c7013ae6c..7b1920a82 100644 --- a//AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.847.md +++ b//AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.847.md @@ -15 +15 @@ This release of Aurora MySQL is compatible with MySQL 8.4.7. For more informatio -For details of the new features in Aurora MySQL version 8.4, see [Aurora MySQL version 8.4 compatible with MySQL 8.4](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL84.html). For differences between Aurora MySQL version 8.4, Aurora MySQL version 3, see [Comparison of Aurora MySQL version 3 and Aurora MySQL version 8.4](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v3-v84.html). For a comparison of Aurora MySQL version 8.4 and MySQL 8.4 Community Edition, see [Comparison of Aurora MySQL version 8.4 and MySQL 8.4 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v84-community.html) in the _Amazon Aurora User Guide_. +For details of the new features in Aurora MySQL version 8.4, see [Aurora MySQL version 8.4 compatible with MySQL 8.4](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL84.html). For differences between Aurora MySQL version 8.4 and version 3, see [Comparison of Aurora MySQL version 3 and Aurora MySQL version 8.4](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v3-v84.html). For a comparison with MySQL 8.4 Community Edition, see [Comparison of Aurora MySQL version 8.4 and MySQL 8.4 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v84-community.html) in the _Amazon Aurora User Guide_. @@ -17 +17 @@ For details of the new features in Aurora MySQL version 8.4, see [Aurora MySQL v -You can perform an in-place major version upgrade, restore a snapshot with upgrade, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 3 cluster into an Aurora MySQL version 8.4.7 cluster. +You can perform an in-place major version upgrade, restore a snapshot with upgrade, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html). You can upgrade from any currently supported Aurora MySQL version 3 cluster to Aurora MySQL version 8.4.7. @@ -31 +31 @@ If you have any questions or concerns, AWS Support is available on the community - * Introduced automatic memory management for Aurora MySQL 8.4 with the new `aurora_enable_memory_management` parameter. When set to `ON` (the default), Aurora automatically manages memory recovery actions to prevent out-of-memory (OOM) database restarts, and the `aurora_oom_response` parameter is ignored. Set `aurora_enable_memory_management` to `OFF` to manually control recovery actions through `aurora_oom_response`. For more information, see [Amazon Aurora MySQL out-of-memory issues](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQLOOM.html) in the _Amazon Aurora User Guide_. + * Introduced automatic memory management for Aurora MySQL 8.4 with the new `aurora_enable_memory_management` parameter. When set to `ON` (the default), Aurora automatically manages memory recovery actions to prevent out-of-memory (OOM) database restarts, and the `aurora_oom_response` parameter is ignored. Set `aurora_enable_memory_management` to `OFF` to control recovery actions manually through `aurora_oom_response`. For more information, see [Amazon Aurora MySQL out-of-memory issues](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQLOOM.html) in the _Amazon Aurora User Guide_. @@ -42 +42 @@ Below are the improvements made compared to Aurora MySQL 3.12.0, see [Aurora MyS - * Fixed an issue that can cause the writer instance to repeatedly restart when the writer instance restarts while purging an undo record for a table with indexes on virtual columns. + * Fixed an issue that can cause the writer instance to repeatedly restart. This occurs when the writer restarts while purging an undo record for a table with indexes on virtual columns. @@ -46 +46 @@ Below are the improvements made compared to Aurora MySQL 3.12.0, see [Aurora MyS - * Fixed an issue where the database writer instance could restart unexpectedly during a global database switchover operation while cleaning up temporary tables after SQL statement processing. This restart could result in longer switchover completion time. + * Fixed an issue where the database writer instance could restart unexpectedly during a global database switchover operation. The restart occurred while cleaning up temporary tables after SQL statement processing. This could result in longer switchover completion time. @@ -67 +67 @@ Below are the improvements made compared to Aurora MySQL 3.12.0, see [Aurora MyS - * Fixed an issue which can cause query results to be returned in ascending order instead of the requested descending order when using `ORDER BY DESC` with a range comparison and `LIMIT`. + * Fixed an issue which can cause query results to be returned in ascending order instead of the requested descending order. This occurs when using `ORDER BY DESC` with a range comparison and `LIMIT`. @@ -69 +69 @@ Below are the improvements made compared to Aurora MySQL 3.12.0, see [Aurora MyS - * Fixed an issue where the reader reports "ERROR 1146" (table not found) during certain online DDL operations on the writer when using INPLACE algorithm. This can occur when either: 1) the reader has not previously opened the table before the DDL begins or 2) the reader restarts or a new reader is created while the DDL is in progress. + * Fixed an issue where the reader reports "ERROR 1146" (table not found) during certain online DDL operations on the writer when using INPLACE algorithm. This can occur when the reader has not previously opened the table before the DDL begins. It can also occur when the reader restarts or a new reader is created while the DDL is in progress. @@ -79 +79 @@ Below are the improvements made compared to Aurora MySQL 3.12.0, see [Aurora MyS - * Fixed an issue that can cause queries using hash joins to return incorrect results when parallel query is enabled and the memory required for a hash join exceeds limit. + * Fixed an issue that can cause queries using hash joins to return incorrect results when parallel query is enabled and the hash join memory requirement exceeds the limit.