[MDEV-16135] Service does not start if date set beyond Y2038 Created: 2018-05-10  Updated: 2018-06-29

Status: Confirmed
Project: MariaDB Server
Component/s: Server
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Michal Schorm Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Hello

You're not going to make timestamps Y2038 compliant. MDEV-341 MDEV-9444

However, if the system has its current date set beyond Y2038, the service won't start.

sql/mysqld.cc; line 3461 (mariadb 5.5.60)

/* TODO: remove this when my_time_t is 64 bit compatible */
 
if (!IS_TIME_T_VALID_FOR_TIMESTAMP(server_start_time))
 
{
 
  sql_print_error("This MySQL server doesn't support dates later than 2038");
 
  return 1;
 
}



 Comments   
Comment by Sergei Golubchik [ 2018-05-10 ]

Of course. You're right.

I just want to note that looking at https://mariadb.org/about/maintenance-policy/ — if I extrapolate the table, and assuming we'll be releasing one major release a year and that we will continue to number new releases 10.X, the first MariaDB version that will be supported in 2038 will be MariaDB-10.18.

So we'll keep the Fix Version/s field of this issue open for now...

Generated at Thu Feb 08 08:26:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.