MySQL Bugs: #119318: When modifying the system time to a date beyond 2038, MySQL installation reports an error

Bug #119318	When modifying the system time to a date beyond 2038, MySQL installation reports an error
Submitted:	6 Nov 2025 11:28	Modified:	23 Jun 7:48
Reporter:	shancun shancun	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Data Dictionary	Severity:	S3 (Non-critical)
Version:	8.4.10	OS:	CentOS (CentOS Linux release 7.7.1908 (Core))
Assigned to:		CPU Architecture:	x86 (x86_64)
Tags:	2038 year, Failed to update tables dictionary object

Description:
1. If the operating system time is changed to a date beyond 2038, such as 2050, when installing MySQL 8.4 or MySQL 9.5, the installation will fail with the error "[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.". When will the version support be released approximately?

2. After installing MySQL 8.4 or MySQL 9.5, if you change the operating system time to a date beyond 2038, such as 2050, you will no longer be able to add or delete fields in tables, nor can you create new tables. An error message will appear stating "3507 - Failed to update tables dictionary object". When will this version be supported?

3. When installing MySQL 8.4 or MySQL 9.5, the timestamp data type still has a maximum storage limit of 2038. Is there any plan to support storage beyond 2038?

How to repeat:
1. Modify the operating system time to a date beyond 2038, for example: `date -s "2050-11-6 19:19:00"`.
2. When installing MySQL 8.4 or 9.5, the installation fails with the error "[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.".
3. After MySQL is installed, if the operating system time is modified to a date beyond 2038, such as: date -s "2050-11-6 19:19:00". Then, when modifying table fields or adding new table fields, a prompt will appear saying "3507 - Failed to update tables dictionary object".

Suggested fix:
It is recommended that the mysql8.x version fully supports the Year 2038 problem. If there is a version plan, please inform me of the specific version and its release date. Thank you very much.

Verified as described.

We are planning an update that will handle this problem in due time.

After verifying the latest release of MySQL 8.4.10, we found that the Year 2038 problem still exists. When modifying the operating system to a date beyond 2038, the newly added tables still report an error "3507 - Failed to update tables dictionary object;". Will this issue be resolved in the next version?