Add new Index advisor user doc

[Oreoxmt]

First-time contributors' checklist

• I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from: Add new Index advisor user doc docs#19867
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[Oreoxmt]

/cc @qiancai

[qiancai]

Rest LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-03-17 02:39:30.772575743 +0000 UTC m=+236864.456811823: ☑️ agreed by qiancai.

[songrijie]

It seems we need include RECOMMEND INDEX in SQL reference, as it's a new syntax.

[songrijie]

Before actually adding the indexes, it's recommended to add invisible indexes, and verify the latency in session with tidb_opt_use_invisible_indexes=on. We shall mention this approach in this doc.

[qw4990]

It seems we need include RECOMMEND INDEX in SQL reference, as it's a new syntax.

I'll submit another PR to add this later.

[qw4990]

Before actually adding the indexes, it's recommended to add invisible indexes, and verify the latency in session with tidb_opt_use_invisible_indexes=on. We shall mention this approach in this doc.

This seems not work because invisible indexes also need to re-org data and cost lots of resources. You mean before removing an index, we can set it to invisible and check?

[Oreoxmt]

/approve

[Oreoxmt]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

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 [Oreoxmt]

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]

In response to a cherrypick label: new pull request created to branch release-8.5: #20184.