*: add execution retry time in slow log and slow_query and statement_summary (#19625)

[ti-srebot]

cherry-pick #19625 to release-4.0

---

Signed-off-by: crazycs520 crazycs520@gmail.com

What problem does this PR solve?

Continue to the previous #19487.

This PR do 2 things:

1. adds Exec_retry_time to indicate the time consuming on retry.

• Exec_retry_time means the useless retry time consuming. Such retry 10 times, total exec_time is 10 seconds, the last successful execution time is 1 second, so the Exec_retry_time is 9 seconds. The last execution time can be found in the Plan field in the slow log.

# Time: 2020-08-31T17:43:07.162845+08:00
# Exec_retry_time: 1.337662279 Exec_retry_count: 2
# Query_time: 1.908441749
# Parse_time: 0.020197318
# Compile_time: 0.02073548

2. adds exec_retry_count and exec_retry_time into system table statement_sammary:

information_schema> select DIGEST_TEXT,SUM_LATENCY,SUM_EXEC_RETRY_TIME,EXEC_COUNT,SUM_EXEC_RETRY from `STATEMENTS_SUMMARY` where SUM_EXEC_RETRY > 0;
+-------------------------------------------+--------------+---------------------+------------+----------------+
| DIGEST_TEXT                               | SUM_LATENCY  | SUM_EXEC_RETRY_TIME | EXEC_COUNT | SUM_EXEC_RETRY |
+-------------------------------------------+--------------+---------------------+------------+----------------+
| select * from t1 where a < ? for update ; | 381395110811 | 263244426899        | 130        | 257            |
+-------------------------------------------+--------------+---------------------+------------+----------------+

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test
• Manual test

Side effects

• Performance regression
  • Consumes more CPU
  • Consumes more MEM

Release note

• Add execution retry time in slow log and slow_query.

[ti-srebot]

/run-all-tests

[crazycs520]

@djshow832 @tangenta PTAL

[crazycs520]

@tangenta @djshow832 PTAL

[lzmhhh123]

LGTM

[djshow832]

LGTM

[crazycs520]

/merge

[ti-srebot]

/run-all-tests