UNIX_TIMESTAMP() does not work with range >= '2038-01-19 03:14:08' UTC

[mjonss]

Bug Report

Please answer these questions before submitting your issue. Thanks!

In MySQL 8.0.28 they increased the range of the argument of UNIX_TIMEZONE() from '2038-01-19 03:14:07.999999' to '3001-01-19 03:14:07.999999' UTC, which TiDB does not support.

(also see #30133)

1. Minimal reproduce step (Required)

set time_zone = UTC;
select unix_timestamp('2038-01-19 03:14:08.000001');

2. What did you expect to see? (Required)

mysql> set time_zone = UTC;
Query OK, 0 rows affected (0,00 sec)

mysql> select unix_timestamp('2038-01-19 03:14:08.000001');
+----------------------------------------------+
| unix_timestamp('2038-01-19 03:14:08.000001') |
+----------------------------------------------+
|                            2147483648.000001 |
+----------------------------------------------+
1 row in set (0,00 sec)

3. What did you see instead (Required)

tidb> set time_zone = UTC;
Query OK, 0 rows affected (0.00 sec)

tidb> select unix_timestamp('2038-01-19 03:14:08.000001');
+----------------------------------------------+
| unix_timestamp('2038-01-19 03:14:08.000001') |
+----------------------------------------------+
|                                     0.000000 |
+----------------------------------------------+
1 row in set (0.00 sec)

4. What is your TiDB version? (Required)

tidb_VERSION(): Release Version: v7.2.0-alpha-216-g6dd86d7e02
Edition: Community
Git Commit Hash: 6dd86d7e0254e9f5ee9ba906b553c3087636cd1a
Git Branch: master
UTC Build Time: 2023-05-18 14:20:59
GoVersion: go1.20.4
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore