metrics: add col/idx name(s) for BackfillProgressGauge and BackfillTotalCounter (#58380)

[ti-chi-bot]

This is an automated cherry-pick of #58380

What problem does this PR solve?

Issue Number: close #58114

Problem Summary:

For BackfillProgressGauge and BackfillTotalCounter, tidb only shows the database name and table name in the metrics. If we add multiple indexes on a single table, it would be difficult to know the rate and progress of each index.

What changed and how does it work?

• Add column names and index names for metrics.

Check List

Tests

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

  • I checked and no code files have been changed.

Test script:

mysql -h 127.0.0.1 -P4000 -uroot -e'create database test1; create database test2;'

sysbench oltp_read_write prepare --db-driver=mysql --mysql-host=127.0.0.1 --mysql-port=4000 --mysql-user=root --mysql-db=test1 --threads=16 --tables=2 --table-size=1000000
sysbench oltp_read_write prepare --db-driver=mysql --mysql-host=127.0.0.1 --mysql-port=4000 --mysql-user=root --mysql-db=test2 --threads=16 --tables=2 --table-size=1000000

# Add Index
mysql -h 127.0.0.1 -P4000 -uroot -e'create index k_pad on test1.sbtest1(pad); alter table test1.sbtest2 add index k_pad(pad), add index k_comp(c, pad);'
mysql -h 127.0.0.1 -P4000 -uroot -e'create index k_pad on test2.sbtest1(pad); alter table test2.sbtest2 add index k_pad(pad), add index k_comp(c, pad);'

# Modify Column
mysql -h 127.0.0.1 -P4000 -uroot -e'alter table test1.sbtest1 change column k k varchar(64); alter table test1.sbtest2 change column k k varchar(64);'
mysql -h 127.0.0.1 -P4000 -uroot -e'alter table test2.sbtest1 change column k k varchar(64); alter table test2.sbtest2 change column k k varchar(64);'

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

Attention: Patch coverage is 89.79592% with 10 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@80db670). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #58530   +/-   ##
================================================
  Coverage               ?   71.1999%           
================================================
  Files                  ?       1468           
  Lines                  ?     423794           
  Branches               ?          0           
================================================
  Hits                   ?     301741           
  Misses                 ?     101519           
  Partials               ?      20534           

Flag	Coverage Δ
unit	71.1999% <89.7959%> (?)

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

Components	Coverage Δ
dumpling	52.9656% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	41.2572% <0.0000%> (?)

[CbcWestwolf]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CbcWestwolf, tangenta

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 [CbcWestwolf,tangenta]
• pkg/ddl/OWNERS [tangenta]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-26 06:28:44.382447094 +0000 UTC m=+1715914.471249633: ☑️ agreed by tangenta.
• 2024-12-26 06:36:57.527517793 +0000 UTC m=+1716407.616320333: ☑️ agreed by CbcWestwolf.