Skip to content

release-22.2: schemachanger/rel: fix race due to failure to clone constraint slots#88802

Merged
ajwerner merged 1 commit intocockroachdb:release-22.2from
ajwerner:backport22.2-88670
Sep 27, 2022
Merged

release-22.2: schemachanger/rel: fix race due to failure to clone constraint slots#88802
ajwerner merged 1 commit intocockroachdb:release-22.2from
ajwerner:backport22.2-88670

Conversation

@ajwerner
Copy link
Copy Markdown
Contributor

@ajwerner ajwerner commented Sep 27, 2022

Backport 1/1 commits from #88670.

/cc @cockroachdb/release


The fundamental race here is that while the slots themselves were being copied by value, the "any" clauses which are a slice were not. The second bug here is that the "inline" values were not being properly reset. That bug could lead to problems when the query was run again in the context of a different element set. We need to reset those inline values too.

Fixes #88628

Release justification: fixes race causing test failures, addresses a GA blocker

Release note: None

The fundamental race here is that while the slots themselves were being copied
by value, the "any" clauses which are a slice were not. The second bug here is
that the "inline" values were not being properly reset. That bug could lead to
problems when the query was run again in the context of a different element
set. We need to reset those inline values too.

Fixes cockroachdb#88628

Release note: None
@ajwerner ajwerner requested a review from a team September 27, 2022 13:29
@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented Sep 27, 2022

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
Copy Markdown
Member

This change is Reviewable

@ajwerner
Copy link
Copy Markdown
Contributor Author

TFTR!

@ajwerner ajwerner merged commit 3bb017b into cockroachdb:release-22.2 Sep 27, 2022
@ajwerner ajwerner deleted the backport22.2-88670 branch September 27, 2022 14:58
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