Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TiDB备份问题
|
username: TiDB超级萌新
Experts, I want to know what this TSO represents. Why do I feel that TSO is so much like a timestamp? But isn’t the timestamp above a specific time? This document is making me confused.
TSO is just a timestamp, right? It’s a crucial part of the TiDB system.
TSO can be understood as the time of data. In databases, specific physical time is generally not used directly as time because there may be multiple changes within one second, which involves precision issues, such as whether to be accurate to milliseconds, microseconds, or nanoseconds. Additionally, physical time can be manually adjusted, and the physical time between multiple nodes may not be the same. Therefore, I think using a logically increasing number as the database time is more appropriate. Of course, this string of numbers is not user-friendly for us personally, so we hope to convert it into physical time for easier operation.
It can be considered a timestamp, but it’s a database timestamp, which has more digits than the system’s.
The SELECT TIDB_PARSE_TSO(446420146007834631) function can directly convert to a timestamp.
You can find it by searching for TSO in the official documentation.
Please explain in detail what was done and how to obtain results without loss.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: