[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Encountered Issues]
[Reproduction Path] What operations were performed to encounter the issue
[Issue Phenomenon and Impact]
[Attachments]
Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.
In my impression, unique indexes created separately are all secondary indexes, right? Does the so-called non-secondary index refer to the index created when the primary key is an int during table creation?
Of course not. A unique index is just an index with the unique keyword added, and it is not directly related to whether it is a secondary index or not, but…
I see. If the secondary index is a unique index, its value stores the primary key index. If the secondary index is a non-unique index, its value stores null, which means that apart from the primary key index, everything else is a secondary index.
This is not entirely correct. In TiDB, the primary key can also be a secondary index. According to h5n1’s statement, except for the clustered index, all others are secondary indexes.