Add more information in slow logs to help analyze slow queries

[qw4990]

Development Task

Now information in slow logs(or slow-query-table) is not enough to analyze slow queries.
After discussing, we should add these useful information into it:

• 1. time-consuming in the parse phase
• 2. time-consuming for compiling the query
• 3. time-consuming for rewriting the query (sessionctx: add some information about the rewriting phase into the slow log #17569)
• 4. time-consuming for optimizing the query (sessionctx: add optimization-time and wait-TS-time into the slow log #17869)
• 5. time-consuming to wait for TSO (sessionctx: add optimization-time and wait-TS-time into the slow log #17869)
• 6. detailed execution information (like results of explain analyze)(UCP: Add execution information in slow log Plan field. #15008)(*: record execute runtime information in slow log #17573)
• 7. if this query hits the plan cache(record whether a statement hit plan cache in slow log #16197)
• 8. if there are subqueries processed in the compile phase (sessionctx: add some information about the rewriting phase into the slow log #17569)
• 9. support ScanDetailV2
• 10. if this query use disk(Show disk usage of a query in slow query and statement summary #16883)

[SunRunAway]

Should Statement Summary be involved?

[breezewish]

@SunRunAway I opened an issue for the statement part. Some fields listed here are already included in the statements. TiDB should provide Slow Query and Statement fields in a unified way, i.e. they have identical fields (or mostly shares a common part) and names.

#17689

[qw4990]

Since pingcap/kvproto#600 is not supported by TiKV, it is no use to support it on TiKV now, so we decide to close this issue now and support it after TiKV supporting it.

[breezewish]

Since pingcap/kvproto#600 is not supported by TiKV, it is no use to support it on TiKV now, so we decide to close this issue now and support it after TiKV supporting it.

@qw4990 There is a PR for it tikv/tikv#7563 Maybe we can drive this PR now.

[breezewish]

@qw4990 Hi, are these new slow log fields available in v4.0 branch?