Mattias Jonsson

My opinion is that we should focus on the older `mysql` command line client from Oracle/MySQL and use that in our documentation. I don't mind if we have a place...

Could possibly be improved by adding log sampling (rate limiting) in the logging configuration, like https://github.com/pingcap/tidb/pull/29362 .

Maybe only use a sample/subset of the partitions to run analyze on for dynamic prune mode?

Example of the same table, but with 8192 hash partitions, taking 2 1/2 hour to complete `ANALYZE TABLE`: ``` tidb> analyze table sbtest1; Query OK, 0 rows affected, 8192 warnings...

@Yisaer, I don't think this is fixed, I just tried to run an `ANALYZE TABLE pt4096` on a similar table with ~1M rows with 4096 hash partitions, and it takes...

> The grammar should be discussed, as the DROP STATS t1, t2 GLOBAL and DROP STATS t PARTITION xxx is not consistent now. I'm not sure whether it's expected, or...

/run-unit-test

/run-mysql-test tidb-test=pr/1975

/run-mysql-test tidb-test=pr/1975

/run-mysql-test tidb-test=pr/1975