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

sqlmigrations: remove ensureMaxPrivileges migration #40583

Merged
merged 1 commit into from
Sep 11, 2019

Conversation

ajwerner
Copy link
Contributor

@ajwerner ajwerner commented Sep 9, 2019

This migration has baked. Furthermore it uses table descriptors in ways I'm
working to change and I want to see it gone.

Release note: None

This migration has baked. Furthermore it uses table descriptors in ways I'm
working to change and I want to see it gone.

Release note: None
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@mberhault mberhault left a comment

Choose a reason for hiding this comment

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

LGTM. While you're there though, might as well remove the other migrations introduced in 2.1.

@ajwerner
Copy link
Contributor Author

While you're there though, might as well remove the other migrations introduced in 2.1.

Err I started do this but ran in to issues where I'm not sure they're all baked in. For example it seems like nothing creates defaultdb other than the migration. I just going to merge this now and we can revisit the others in a separate commit.

bors r=mberhault

@craig
Copy link
Contributor

craig bot commented Sep 11, 2019

Build failed (retrying...)

@ajwerner
Copy link
Contributor Author

flaked with #31287

bors r+

@craig
Copy link
Contributor

craig bot commented Sep 11, 2019

Already running a review

craig bot pushed a commit that referenced this pull request Sep 11, 2019
40583: sqlmigrations: remove ensureMaxPrivileges migration r=mberhault a=ajwerner

This migration has baked. Furthermore it uses table descriptors in ways I'm
working to change and I want to see it gone.

Release note: None

40669: opt: fix execbuilder output column count for lookup joins r=rytaft a=rytaft

This commit fixes a bug in the `execbuilder`, which was determining
the number of output columns incorrectly for lookup joins. In particular,
if the join was a semi- or anti-join, the `execbuilder` was incorrectly
including the right side columns in the column count. This commit
fixes the code so it only includes left side columns for semi- and
anti-joins.

This commit also fixes a bug in the DistSQL planner that was masked
by the bug in the `execbuilder`. In particular, the output types slice
for lookup semi- and anti-joins incorrectly included the types from the
right side columns. This commit fixes it to only include types for the
left side columns.

Fixes #40562

Release note (bug fix): Fixed an error that could occur when the
optimizer created a plan with a lookup semi- or anti-join nested
inside of another join.

Co-authored-by: Andrew Werner <ajwerner@cockroachlabs.com>
Co-authored-by: Rebecca Taft <becca@cockroachlabs.com>
@craig
Copy link
Contributor

craig bot commented Sep 11, 2019

Build succeeded

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.

3 participants