How TiDB Traces Sessions

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiDB如何做会话的trace

| username: alfred

【TiDB Usage Environment】Production Environment / Testing / POC
【TiDB Version】
【Encountered Issues】
【Reproduction Path】What operations were performed that led to 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.

2
| username: 啦啦啦啦啦 | Original post link

Refer to this

3
| username: forever | Original post link 
{
  "trace": [
    {
      "id": 1,
      "start_ts": "2023-10-01T12:00:00Z",
      "duration": 12345,
      "operation": "select",
      "details": {
        "table": "tablename",
        "columns": ["*"]
      }
    }
  ]
}
4
| username: alfred | Original post link

Yes, “TRACE statement is an extension of MySQL syntax by TiDB,” but the level of detail obtained from trace is much worse compared to Oracle.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.