sessionctx: mark tidb_enable_auto_analyze_priority_queue as deprecated

[0xPoe]

What problem does this PR solve?

Issue Number: close None

Problem Summary:

What changed and how does it work?

Mark TiDBEnableAutoAnalyzePriorityQueue as deprecated.

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.

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.

将 tidb_enable_auto_analyze_priority_queue 标记为弃用，总是使用优先级队列来调度 auto-analyze
Mark tidb_enable_auto_analyze_priority_queue as deprecated, always use priority queue for auto-analyze scheduling

[Copilot]

Pull Request Overview

This PR marks the tidb_enable_auto_analyze_priority_queue system variable as deprecated, enforcing that TiDB will always use a priority queue for auto-analyze scheduling.

• Changes the validation logic to reject attempts to disable the setting
• Adds deprecation comments to the variable definition
• Improves code formatting in the system variable definition

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
pkg/sessionctx/variable/sysvar.go	Updates validation logic to enforce priority queue usage and improves formatting
pkg/sessionctx/vardef/tidb_vars.go	Adds deprecation comment to the variable definition

Comments suppressed due to low confidence (1)

pkg/sessionctx/variable/sysvar.go:1117

• [nitpick] The error message should be more consistent with typical deprecation patterns. Consider using 'Setting X to OFF is no longer supported' format for clarity.

				return "", errors.New("tidb_enable_auto_analyze_priority_queue has been deprecated and TiDB will always use priority queue to schedule auto analyze.")

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.3460%. Comparing base (f13696c) to head (4842702).
⚠️ Report is 36 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #62659        +/-   ##
================================================
+ Coverage   72.8568%   74.3460%   +1.4892%     
================================================
  Files          1776       1822        +46     
  Lines        486675     507489     +20814     
================================================
+ Hits         354576     377298     +22722     
+ Misses       110465     107798      -2667     
- Partials      21634      22393       +759     

Flag	Coverage Δ
integration	46.2921% <0.0000%> (?)
unit	73.1550% <100.0000%> (+0.9761%)	⬆️

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

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	46.3302% <ø> (-0.0054%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[0xPoe]

/test all

[ti-chi-bot]

@0xPoe: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
non-block-pull-unit-test-next-gen	77dcc75	link	false	/test pull-unit-test-next-gen
non-block/pull-unit-test-next-gen	4842702	link	false	/test pull-unit-test-next-gen
non-block/pull-mysql-client-test-next-gen	4842702	link	false	/test pull-mysql-client-test-next-gen
non-block/pull-mysql-test-next-gen	4842702	link	false	/test pull-mysql-test-next-gen
non-block/pull-integration-e2e-test-next-gen	4842702	link	false	/test pull-integration-e2e-test-next-gen

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[0xPoe]

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

• Code compiles successfully

• Unit tests added

• All tests pass

• Bazel files updated

• Comments added where necessary

• PR title and description updated

• Documentation PR created (pingcap/docs#21526)

• PR size is reasonable

/cc @terry1purcell @time-and-fate

[terry1purcell]

/lgtm

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-08-06 13:54:23.823459795 +0000 UTC m=+449173.966220990: ☑️ agreed by terry1purcell.
• 2025-08-06 14:00:40.092367206 +0000 UTC m=+449550.235128381: ☑️ agreed by time-and-fate.

[yudongusa]

Please also open a document PR.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terry1purcell, time-and-fate, yudongusa

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:

• pkg/sessionctx/vardef/OWNERS [yudongusa]
• pkg/sessionctx/variable/OWNERS [yudongusa]
• pkg/statistics/OWNERS [terry1purcell,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