opt: improve query plans on tables with ascending keys #83431
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-sql-queries
SQL Queries Team
This ascending query problem is a common problem for database optimizers. The problem is that the optimizer assumes that a columns has zero or very few values outside of the maximum (and minimum) values in the collected histograms. If newly inserted values are ever-increasing, then the optimizer can wildly underestimate the rows that match filters for the latest values, leading to query plans with very poor performance.
A detailed description of the problem can be found at #64570 (comment).
Jira issue: CRDB-17067
Epic: CRDB-13963
The text was updated successfully, but these errors were encountered: