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

release-23.1: sql: fix circular dependencies in views #100159

Merged

Conversation

rharding6373
Copy link
Collaborator

@rharding6373 rharding6373 commented Mar 30, 2023

Backport 1/1 commits from #99174.

/cc @cockroachdb/release


This change fixes node crashes that could happen due to stack overflow if views were created with circular dependencies.

Fixes: #98999
Epic: none
Co-authored-by: [email protected]

Release note (bug fix): If views are created with circular dependencies, CRDB returns the error "cyclic view dependency for relation" instead of crashing the node. This bug is present since at least 21.1.

Release justification: Fixes a bug that can cause the gateway node to
crash if there are self-referencing views.

@rharding6373 rharding6373 requested review from mgartner and a team March 30, 2023 16:40
@rharding6373 rharding6373 requested a review from a team as a code owner March 30, 2023 16:40
@blathers-crl
Copy link

blathers-crl bot commented Mar 30, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

This change fixes node crashes that could happen due to stack overflow
if views were created with circular dependencies. It also fixes a few
places in the schema changer where there were problems dropping views
with circular dependencies.

Fixes: cockroachdb#98999
Epic: none
Co-authored-by: [email protected]

Release note (bug fix): If views are created with circular dependencies,
CRDB returns the error "cyclic view dependency for
relation" instead of crashing the node. This bug is present since at
least 21.1.

Release justification: Fixes a bug that can cause the gateway node to
crash if there are self-referencing views.
@rharding6373 rharding6373 merged commit 244c452 into cockroachdb:release-23.1 Mar 30, 2023
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