You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TiDB calculates time zones using the system's built-in tzinfo database, while TiKV calculates time zones using the embedded tzinfo database in the TiKV code (current version is 2018; fixed version is 2020). Therefore, when encountering time zones with DST rule changes after 2018, there are inconsistencies in the calculated results.
In #49586, the client's scenario is Brazil, where DST was discontinued from 2020 to 2023. However, TiKV incorrectly assumes that Brazil still follows DST during calculations.
The text was updated successfully, but these errors were encountered:
IMO TiKV should just drop chrono-tz and replace it with e.g. hourglass that loads the tzdata directly from the OS rather than relying on those hard-coded into the binary.
Enhancement
related issues:
#49586
#29427
tikv/tikv#16220
TiDB calculates time zones using the system's built-in tzinfo database, while TiKV calculates time zones using the embedded tzinfo database in the TiKV code (current version is 2018; fixed version is 2020). Therefore, when encountering time zones with DST rule changes after 2018, there are inconsistencies in the calculated results.
In #49586, the client's scenario is Brazil, where DST was discontinued from 2020 to 2023. However, TiKV incorrectly assumes that Brazil still follows DST during calculations.
The text was updated successfully, but these errors were encountered: