initStatsTopN4Chunk()
doesn't sort TopN for statistics sometimes
#34216
Labels
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.0
component/statistics
severity/moderate
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
As the title says, the logic of
initStatsTopN4Chunk()
is not correct. The stats for all tables are handled here, but it assumes it's handling stats on one table. The TopNs of different tables that have the same column ID are not guaranteed to be sorted.The text was updated successfully, but these errors were encountered: