Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sql: better control over selecting columns to collect stats for #139382

Open
mgartner opened this issue Jan 17, 2025 · 1 comment
Open

sql: better control over selecting columns to collect stats for #139382

mgartner opened this issue Jan 17, 2025 · 1 comment
Labels
A-sql-table-stats Table statistics (and their automatic refresh). C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-2 Issues/test failures with a fix SLA of 3 months T-sql-queries SQL Queries Team

Comments

@mgartner
Copy link
Collaborator

mgartner commented Jan 17, 2025 •
edited by cockroach-jira-scripts
Loading

Currently the database decides which columns to collect statistics for, and which of those to sample and generate histograms for. There should be a way for a user to turn off or force stats for specific columns. I think the most useful feature to start with would be to allow a user to disable or force sampling and histograms on specific columns. This could help mitigate issues like #139381.

Jira issue: CRDB-46618
@mgartner mgartner added A-sql-table-stats Table statistics (and their automatic refresh). C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs labels Jan 17, 2025
@github-project-automation github-project-automation bot moved this to Triage in SQL Queries Jan 17, 2025
@mgartner mgartner added the P-2 Issues/test failures with a fix SLA of 3 months label Jan 17, 2025
@exalate-issue-sync exalate-issue-sync bot added the T-sql-queries SQL Queries Team label Jan 21, 2025
@mgartner mgartner mentioned this issue Jan 27, 2025
Open
@michae2 michae2 moved this from Triage to 25.2 Release in SQL Queries Jan 28, 2025
@michae2 michae2 added the E-quick-win Likely to be a quick win for someone experienced. label Jan 28, 2025
@michae2
Copy link
Collaborator

michae2 commented Jan 28, 2025

[triage] we have to think about the UX. we do have the WITH syntax, could add to that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-sql-table-stats Table statistics (and their automatic refresh). C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-2 Issues/test failures with a fix SLA of 3 months T-sql-queries SQL Queries Team
Projects
SQL Queries
Status: 25.2 Release
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mgartner @michae2