-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: implement vectorized operator for table statistics collection #41203
Copy link
Copy link
Open
Labels
A-sql-table-statsTable statistics (and their automatic refresh).Table statistics (and their automatic refresh).A-sql-vecSQL vectorized engineSQL vectorized engineC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-queriesSQL Queries TeamSQL Queries Teamo-perf-efficiencyRelated to performance efficiencyRelated to performance efficiency
Description
Automatic statistics (delivered in 19.1) can consume a large number of resources and take a large amount of time in certain circumstances. Using the vectorized execution framework for stats can reduce the impact of running statistics on the CBO ensuring that users continue to leave automatic statistics turned on. Without automatic stats (or manually created stats) the optimizer may make suboptimal decisions.
Epic: CRDB-747
Jira issue: CRDB-5482
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-sql-table-statsTable statistics (and their automatic refresh).Table statistics (and their automatic refresh).A-sql-vecSQL vectorized engineSQL vectorized engineC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-queriesSQL Queries TeamSQL Queries Teamo-perf-efficiencyRelated to performance efficiencyRelated to performance efficiency
Type
Projects
Status
Backlog