Skip to content

Commit b131f8c

Browse files
authored
Update august-2024.md
1 parent 99aacee commit b131f8c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mysql/flexible-server/release-notes/august-2024.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Existing engine version >=8.0.34 server upgrades to 8.0.37 engine version.
1717
To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
1818

1919
> [!NOTE]
20-
> Percona has identified a [critical bug](https://www.percona.com/blog/do-not-upgrade-to-any-version-of-mysql-after-8-0-37/?utm_campaign=2024-blog-q3&utm_content=300046226&utm_medium=social&utm_source=linkedin&hss_channel=lcp-421929) in MySQL versions 8.0.38, 8.4.1, and 9.0.0 that causes the MySQL daemon to crash upon restart if over 10,000 tables exist. While Azure MySQL will not upgrade to these versions in the August maintenance, our managed service limits table spaces to 1,000, effectively preventing this issue and ensuring our customers remain unaffected. We will closely monitor the MySQL community for further developments.
20+
> Percona has identified a [critical bug](https://www.percona.com/blog/do-not-upgrade-to-any-version-of-mysql-after-8-0-37/?utm_campaign=2024-blog-q3&utm_content=300046226&utm_medium=social&utm_source=linkedin&hss_channel=lcp-421929) in MySQL versions 8.0.38, 8.4.1, and 9.0.0 that causes the MySQL daemon to crash upon restart if over 10,000 tables exist. Azure MySQL will not upgrade to the buggy MySQL versions 8.0.38, 8.4.1, and 9.0.0 in the August maintenance. Instead, we will skip these versions and upgrade directly to a future MySQL engine version that has resolved this issue. Microsoft Azure MySQL remains committed to providing our customers with the most secure and stable PaaS database service.
2121
2222
## Features
2323
No new features are being introduced in this maintenance update.

0 commit comments

Comments
 (0)