Show ANALYZE TABLE result

Description

TiDB> ANALYZE TABLE t1;
Query OK, 0 rows affected (0.05 sec)

mysql> ANALYZE TABLE t1;
+----------------------+---------+----------+----------+
| Table                | Op      | Msg_type | Msg_text |
+----------------------+---------+----------+----------+
| invisible_indexes.t1 | analyze | status   | OK       |
+----------------------+---------+----------+----------+
1 row in set (0.05 sec)

Contributor guide

Tech stack

gosql

Domain

database

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Familiarity with GoUnderstanding of TiDB SQL execution

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

30

Research direction

Look into the TiDB execution layer where ANALYZE TABLE is handled (likely in the executor package). Currently, the statement returns '0 rows affected' instead of a result set with columns like Table, Op, Msg type, Msg text. Study how MySQL returns results for ANALYZE TABLE and modify the TiDB code to produce a similar result. Check if there's a mechanism to return result sets for DDL like statements. The issue may require changes in the plan builder and executor to generate a result set. Reference the MySQL documentation for the expected output format.