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.

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

sql: display postqueries in EXPLAIN #38340

Closed
yuzefovich opened this issue Jun 21, 2019 · 2 comments · Fixed by #38849
Closed

sql: display postqueries in EXPLAIN #38340

yuzefovich opened this issue Jun 21, 2019 · 2 comments · Fixed by #38849
Assignees
Labels
A-sql-fks C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@yuzefovich
Copy link
Member

We're introducing postqueries in #38281, but they won't show up in the output of EXPLAIN at the moment. We should fix that.

@yuzefovich yuzefovich added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-sql-fks labels Jun 21, 2019
@yuzefovich yuzefovich self-assigned this Jun 21, 2019
@RaduBerinde
Copy link
Member

We will need this soon (for writing tests for opt-driven FK checks).

@yuzefovich
Copy link
Member Author

Sorry for the delay on this. I'll be working on this once I finish with finalizing vectorize settings to turn on a part of the engine by default.

craig bot pushed a commit that referenced this issue Jul 15, 2019
38849: sql: display postqueries in EXPLAIN r=yuzefovich a=yuzefovich

Postqueries are now displayed in the output of EXPLAIN statement.

Fixes: #38340.

Release note: None

Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com>
@craig craig bot closed this as completed in #38849 Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-sql-fks C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants