Hi! Thanks for the reply and further context. I am now testing running mariadb-test-run in 2038 in CI with libfaketime at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/74, I will report later how it goes. On Sun, 3 Mar 2024 at 05:43, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Otto,
MDEV-32188 is blocked by MDEV-33449 "improving repair of tables", because repair changes are required to solve the upgrade of system versioned tables to new timestamps.
Current plan is to get everything into 11.5.
Regards, Sergei Chief Architect, MariaDB Server and security@mariadb.org
On Mar 02, Otto Kekäläinen via developers wrote:
Hi!
Related to this topic I noticed that MariaDB currently has a hard failure if started in 2038+
# date Thu Mar 3 05:55:28 UTC 2039
# ./sql/mariadbd --version 2039-03-03 5:58:55 0 [ERROR] This server doesn't support dates later than 2038
This is due to https://github.com/MariaDB/server/blob/11.5/sql/mysqld.cc#L3903-L3908
/* 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 server doesn't support dates later than 2038"); exit(1); }
I see that MDEV-32188 is now "in testing". I wonder how that test was done, did you remove this check in order to get the server starting on a machine that has time set to 2039?