statistics: always tracking predicate columns

[Rustin170506]

What problem does this PR solve?

Issue Number: ref #53567

Problem Summary:

What changed and how does it work?

You can find the more detailed design here: #53511

• Marked TiDBEnableColumnTracking and TiDBDisableColumnTrackingTime as deprecated.
• Always enable predicate column tracking.
• Removed use of EnableColumnTracking and TiDBDisableColumnTrackingTime.

Check List

Tests

• Unit test
• Integration test
• Manual test
• No need to test

  • I checked and no code files have been changed.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 55.9384%. Comparing base (f57d2b9) to head (794a650).
Report is 4 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54152         +/-   ##
=================================================
- Coverage   72.8354%   55.9384%   -16.8971%     
=================================================
  Files          1520       1640        +120     
  Lines        434902     605433     +170531     
=================================================
+ Hits         316763     338670      +21907     
- Misses        98541     243641     +145100     
- Partials      19598      23122       +3524     

Flag	Coverage Δ
integration	37.0097% <70.0000%> (?)
unit	71.8311% <100.0000%> (+0.0121%)	⬆️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	52.7442% <ø> (+6.6156%)	⬆️

[Rustin170506]

🔢 Self-check (PR reviewed by myself and ready for feedback.)

[Rustin170506]

Tested locally:

1. Start the TiDB cluster with patch: tiup playground v8.1.0 --db.binpath /Volumes/t7/code/tidb/bin/tidb-server
2. Try to set TiDBEnableColumnTracking: set global tidb_enable_column_tracking = 0

mysql> set global tidb_enable_column_tracking = 0
    -> ;
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> show warnings;
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                                |
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1681 | The 'tidb_enable_column_tracking' variable is deprecated and will be removed in future versions of TiDB. It is always set to 'ON' now. |
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

3. Check its value:

mysql> select @@tidb_enable_column_tracking;
+-------------------------------+
| @@tidb_enable_column_tracking |
+-------------------------------+
|                             1 |
+-------------------------------+
1 row in set (0.00 sec)

4. Create a table:

use test;
create table t(a int, b int);

5. Select from the table: select * from t where a = 1
6. Check the predicate columns table(wait for 5 minutes):

select * from mysql.column_stats_usage;
mysql> select * from mysql.column_stats_usage;
+----------+-----------+---------------------+------------------+
| table_id | column_id | last_used_at        | last_analyzed_at |
+----------+-----------+---------------------+------------------+
|      104 |         1 | 2024-06-21 14:58:14 | NULL             |
+----------+-----------+---------------------+------------------+
1 row in set (0.00 sec)

7. Analyze the table: analyze table t

mysql> select * from mysql.analyze_jobs;
+----+---------------------+--------------+------------+----------------+--------------------------------------------------------------------+----------------+---------------------+---------------------+----------+-------------+----------------+------------+
| id | update_time         | table_schema | table_name | partition_name | job_info                                                           | processed_rows | start_time          | end_time            | state    | fail_reason | instance       | process_id |
+----+---------------------+--------------+------------+----------------+--------------------------------------------------------------------+----------------+---------------------+---------------------+----------+-------------+----------------+------------+
|  1 | 2024-06-21 14:55:13 | test         | t          |                | analyze table all columns with 256 buckets, 100 topn, 1 samplerate |              0 | 2024-06-21 14:55:13 | 2024-06-21 14:55:13 | finished | NULL        | 127.0.0.1:4000 |       NULL |
+----+---------------------+--------------+------------+----------------+--------------------------------------------------------------------+----------------+---------------------+---------------------+----------+-------------+----------------+------------+
1 row in set (0.00 sec)

[Rustin170506]

🔢 Self-check (PR reviewed by myself and ready for feedback.)

[Rustin170506]

🔢 Self-check (PR reviewed by myself and ready for feedback.)

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-06-21 08:08:44.200133478 +0000 UTC m=+361450.685622310: ☑️ agreed by qw4990.
• 2024-06-21 08:17:29.77504754 +0000 UTC m=+361976.260536372: ☑️ agreed by AilinKid.

[easonn7]

/approve

[fixdb]

+1

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, easonn7, fixdb, qw4990

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 [AilinKid,fixdb,qw4990]
• pkg/planner/OWNERS [AilinKid,fixdb,qw4990]
• pkg/sessionctx/variable/OWNERS [easonn7]
• pkg/statistics/OWNERS [AilinKid,fixdb,qw4990]

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

[Rustin170506]

/retest