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

opt: improve explain (opt,env) #37402

Open
4 of 7 tasks
justinj opened this issue May 8, 2019 · 3 comments
Open
4 of 7 tasks

opt: improve explain (opt,env) #37402

justinj opened this issue May 8, 2019 · 3 comments
Labels
A-sql-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. T-sql-queries SQL Queries Team
Projects
BACKLOG, NO NEW ISSUES: SQL Optimizer SQL Queries

Comments

@justinj
Copy link
Contributor

justinj commented May 8, 2019 •
edited by mgartner

Tracker issue for improvements to EXPLAIN (opt, env) / EXPLAIN ANALYZE (DEBUG):

  • include distsql plan
  • include tables referenced by foreign keys (or remove unimportant foreign key references)
  • include INTERLEAVE IN parent tables
  • create the tables in an order that works (topological sort)
  • make sure the fully qualified names are correct
  • include histograms in the INJECT STATISTICS commands
  • include the node's locality information

Jira issue: CRDB-4433
@justinj justinj added S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. A-sql-optimizer SQL logical planning and optimizations. labels May 8, 2019
@justinj justinj self-assigned this May 8, 2019
@awoods187 awoods187 added this to To do in BACKLOG, NO NEW ISSUES: SQL Optimizer via automation Jun 21, 2019
@awoods187 awoods187 added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Jun 21, 2019
@RaduBerinde RaduBerinde moved this from Triage to Higher Priority Backlog in BACKLOG, NO NEW ISSUES: SQL Optimizer Sep 10, 2019
@rytaft
Copy link
Collaborator

rytaft commented Dec 18, 2019

We should also add histograms

@RaduBerinde RaduBerinde mentioned this issue Dec 21, 2019
Closed
@RaduBerinde RaduBerinde moved this from Higher Priority Backlog to Functional issues in BACKLOG, NO NEW ISSUES: SQL Optimizer Apr 18, 2020
@RaduBerinde RaduBerinde moved this from Functional issues to Infrastructure in BACKLOG, NO NEW ISSUES: SQL Optimizer Apr 18, 2020
@RaduBerinde RaduBerinde mentioned this issue Oct 27, 2020
Closed
@jlinder jlinder added the T-sql-queries SQL Queries Team label Jun 16, 2021
@michae2
Copy link
Collaborator

michae2 commented Aug 2, 2021

Also missing sequences.

@michae2 michae2 added this to Triage in SQL Queries via automation Aug 2, 2021
@michae2
Copy link
Collaborator

michae2 commented Aug 2, 2021

Also missing CREATE DATABASE statements.

@cucaroach cucaroach moved this from Triage to Backlog in SQL Queries Aug 3, 2021
@mgartner mgartner moved this from Backlog (DO NOT ADD NEW ISSUES) to New Backlog in SQL Queries May 25, 2023
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-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. T-sql-queries SQL Queries Team
Projects
BACKLOG, NO NEW ISSUES: SQL Optimizer
Infrastructure & performance
SQL Queries
Status: Backlog
SQL Queries
New Backlog
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jlinder @justinj @rytaft @awoods187 @michae2