cockroachdb / cockroachdb/cockroach
sql: automate a way to discover the most "important" internal queries
Open
C-enhancement
T-sql-queries
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
It would be great if we had a way to discover that a new "important" internal query is introduced. "Important" here can mean "frequently issued", or "expensive to execute", or something other metric. We then could use this query set to ensure that all queries have good plans.
One way to achieve this I imagine would be to introduce a new roachtest that runs some workload for a period of time. We'd teach the internal executor to somehow track (maybe keep in memory or log it) all queries throughout the roachtest run, and then we'd aggregate all the executions to find the "important" queries.
Jira issue: CRDB-30422
Contributor guide
Assessment
This issue has not been assessed yet.