statistics: split lock stats handler and rewrite the insert SQL

[Rustin170506]

What problem does this PR solve?

Issue Number: ref #46351

Problem Summary:

What is changed and how it works?

• Split the lock stats handler.
• Split the AddLockedTables function to small functions.
• Rewrote the INSERT SQL.
• Only try to execute the SQL if the table is not locked.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[codecov]

Codecov Report

Merging #46403 (31d4eff) into master (c9b8d9c) will decrease coverage by 0.6781%.
Report is 32 commits behind head on master.
The diff coverage is 56.4220%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #46403        +/-   ##
================================================
- Coverage   73.4051%   72.7270%   -0.6782%     
================================================
  Files          1293       1322        +29     
  Lines        393587     402490      +8903     
================================================
+ Hits         288913     292719      +3806     
- Misses        86314      91363      +5049     
- Partials      18360      18408        +48     

Flag	Coverage Δ
integration	25.7840% <5.0458%> (?)
unit	73.5655% <56.4220%> (+0.1604%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.1752% <ø> (+0.1118%)	⬆️
br	47.9509% <ø> (-4.4156%)	⬇️

[Rustin170506]

1. Start the TiDB cluster: tiup playground nightly --tiflash 0 --db.binpath /Users/hi-rustin/GolandProjects/tidb/bin/tidb-server
2. Create table and analyze it:

create table t(a int, b int);
insert into t values (1,2), (3,4), (5,6), (7,8);
analyze table t;
show warnings;

3. Lock table: lock stats t;
4. Analyze it again: analyze table t;
5. Check the warnings: show warnings;

mysql> show warnings;
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                                 |
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------+
| Note    | 1105 | Analyze use auto adjusted sample rate 1.000000 for table test.t, reason to use this rate is "use min(1, 110000/4) as the sample-rate=1" |
| Warning | 1105 | skip analyze locked table: t                                                                                                            |
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------+

6. Check the mysql.stats_table_locked table:

mysql> use mysql;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> select * from stats_table_locked;
+----------+--------------+-------+--------------------+
| table_id | modify_count | count | version            |
+----------+--------------+-------+--------------------+
|       98 |            4 |     4 | 443863948666601483 |
+----------+--------------+-------+--------------------+
1 row in set (0.00 sec)

7. Try to lock it again: lock stats t;

mysql> use test;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> lock stats t;
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> show warnings;
+---------+------+-----------------------------------+
| Level   | Code | Message                           |
+---------+------+-----------------------------------+
| Warning | 1105 | skip locking locked table: test.t |
+---------+------+-----------------------------------+
1 row in set (0.00 sec)

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-08-28 11:49:07.036336878 +0000 UTC m=+1754911.585352865: ☑️ agreed by qw4990.
• 2023-08-29 04:01:41.218691489 +0000 UTC m=+1813265.767707476: ☑️ agreed by time-and-fate.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, qw4990, time-and-fate

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hawkingrei,qw4990,time-and-fate]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Rustin170506]

/retest