Enhancement
The optimizer chose the wrong sample rate to analyze a big table and then caused TiDB OOM, but now we cannot know why this wrong sample rate is chosen from the log.
It's better to log the reason why the sample rate is chosen for this table when analyzing:
