Is there a problem with the CURRENT_TIMESTAMP(6) function?

There are also limitations;

The experiment sees the truth, I hope it will help you, if you have any help, please click to accept, thank you

There are also limitations;

The experiment sees the truth, I hope it will help you, if you have any help, please click to accept, thank you

I tested with 8.0.Also have this problem.

Screenshot from:
https://www.modb.pro/db/130918

I hope this helps you

In this way, MYSQL 2038 is fully limited

Will there be another time zone conversion operation?

Two experiments again. After changing the system time to 2038, the entire mysql database collapsed. It should be the timestamp used in mysql, which caused mysql to crash.I don't know if other versions have fixed this issue.
I only have version 5.6 now.

Ask whether the CURRENT_TIMESTAMP(6) function of MYSQL ON UPDATE CURRENT_TIMESTAMP(6) has the same time zone conversion cost as the TIMESTAMP field type? For example, the time zone is set to SYSTEM
https://mp.weixin.qq.com/s/AtyaIP92L6KnZFB9bQA3ug
MySQL parameter time_zone causes high online sys cpu

The conclusion of the article clearly states that the partition conversion is caused by time_zone = system.

It is recommended to replace TIMESTAMP with datetime;
Content interception: https://wenku.baidu.com/view/efc469e0b84cf7ec4afe04a1b0717fd5370cb24d.html