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

opt: specify hash joins in EXPLAIN (OPT) #38827

Merged
merged 1 commit into from
Jul 11, 2019

Conversation

RaduBerinde
Copy link
Member

In EXPLAIN (OPT), joins that have no mention (like merge or
lookup) are executed as hash joins. Make this explicit, for the
benefit of usage outside of the opt team.

Release note: None

In EXPLAIN (OPT), joins that have no mention (like `merge` or
`lookup`) are executed as hash joins. Make this explicit, for the
benefit of usage outside of the opt team.

Release note: None
@RaduBerinde RaduBerinde requested a review from a team as a code owner July 11, 2019 19:49
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Member

@jordanlewis jordanlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this is going to be really helpful for users.

Copy link
Contributor

@justinj justinj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just looked at expr_format.go and peeked at a couple of the tests, :lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @justinj and @rytaft)

@RaduBerinde
Copy link
Member Author

Thanks, this is going to be really helpful for users.

Is it? I thought we advertise the simple EXPLAIN to users and mostly use the OPT variant internally?

@jordanlewis
Copy link
Member

Is it? I thought we advertise the simple EXPLAIN to users and mostly use the OPT variant internally?

My understanding is that we were planning to deprecate simple EXPLAIN and switch the default to what OPT produced, but now that I think about it, I don't remember how I got that understanding.

@RaduBerinde
Copy link
Member Author

bors r+

craig bot pushed a commit that referenced this pull request Jul 11, 2019
38663: sql: add support for NOT VALID Foreign Key constraints r=Tyler314 a=Tyler314

Implemented the support of not validating an ALTER TABLE foreign key constraint to a table. Within alter_table.go we set the validity of the foreign key reference to be unvalidated, and within shema_changer.go we then check the case where the foreign key being added is unvalidated and do not check its validity.

This allows users to create a reference between two non-empty tables who's entries don't comply with the constraint when it's first added.

38827: opt: specify hash joins in EXPLAIN (OPT) r=RaduBerinde a=RaduBerinde

In EXPLAIN (OPT), joins that have no mention (like `merge` or
`lookup`) are executed as hash joins. Make this explicit, for the
benefit of usage outside of the opt team.

Release note: None

Co-authored-by: craig[bot] <bors@cockroachlabs.com>
Co-authored-by: Tyler314 <tyler@cockroachlabs.com>
Co-authored-by: Radu Berinde <radu@cockroachlabs.com>
@craig
Copy link
Contributor

craig bot commented Jul 11, 2019

Build succeeded

@craig craig bot merged commit 5713aa6 into cockroachdb:master Jul 11, 2019
@RaduBerinde RaduBerinde deleted the explain-show-hashjoin branch July 13, 2019 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants