-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
60719: sql/opt: propagate row-level locking mode to index, lookup, inverted, and zigzag joins r=nvanbenschoten a=nvanbenschoten Fixes #56941. The first commit updates the execbuilder to propagate row-level locking modes through transformations from standard Scan and Join operations to specialized IndexJoin, LookupJoin, and InvertedJoin operations. The second commit updates the execbuilder to propagate row-level locking modes through transformations from standard Scan and Join operations to ZigZagJoins, and allows for the use of zigzag joins when explicit row-level locking modes are in use. Release note (sql change): table scans performed as a part of index joins, lookup joins, and inverted joins now respect the row-level locking strength and wait policy specified by the optional FOR SHARE/UPDATE [NOWAIT] clause on SELECT statements. Release note (sql change): table scans performed as a part of zigzag joins now respect the row-level locking strength and wait policy specified by the optional FOR SHARE/UPDATE [NOWAIT] clause on SELECT statements. 80070: sql: do not close stmt buffer of internal executor in errCallback r=yuzefovich a=yuzefovich Previously, we would close the stmt buffer of the internal executor in `errCallback`, "just to be safe" since it was assumed that the buffer is already closed when the callback is executed. The callback runs whenever `run()` loop of connExecutor exits with an error. However, it is possible for the following sequence of events to happen: - The new goroutine is spun up for the internal executor before any commands are pushed into the stmt buffer. - The context is canceled before the new goroutine blocks waiting for the command to execute, i.e. `run()` loop is exited before any commands are executed. - The `errCallback` with the context cancellation error is evaluated. This closes the stmt buffer. The goroutine exits. - The main goroutine tries to push some commands into the buffer only to find that it was already closed. An assertion error is returned, and a sentry event is created. I think we should just not close the stmt buffer in the `errCallback` since this was never necessary and can lead to the scenario described above where no sentry event should be emitted. Fixes: #79746. Release note: None 80190: kvserver: version gate locality-aware load-based rebalancing r=aayushshah15 a=aayushshah15 This commit introduces a set of deprecated store rebalancer methods corresponding to the pre-22.1 load-rebalancing scheme. Until a store detects that the version upgrade (to 22.1) has been finalized, the store will fall back to the old (pre-22.1) load-based rebalancing logic that wasn't locality aware. This is done in order to minimize risk of unexpected behavior in mixed version clusters. All the tests corresponding to the old logic have been re-introduced, and are unchanged. Resolves #76702 Release note: None 80263: bazel: run `returncheck` lint in `nogo` r=rail a=rickystewart Unfortunately `returncheck` is not implemented as an `Analyzer` so it can't be integrated with `nogo` directly. Instead I've copied/adapted the existing code from https://github.com/cockroachdb/returncheck. The vendored `returncheck` can be deleted from tree when we no longer need to support `make lint`. Closes #73391. Release note: None 80317: bazel,dev: provide opt-out for building w/ `nogo` r=rail a=rickystewart Now we provide `--//build/toolchains:nogo_disable` as an option which will force `nogo` checks OFF even if you have globally configured `lintonbuild`. This can be used by end users for builds but primarily I want a way to force builds to finish faster when `nogo` checks are not particularly useful: namely, when building `dev` for the first time (via the `dev` script) and when building the `bazel-remote` binary. Also have `dev build` infer when passing `nogo_disable` will be OK and pass it in when appropriate. Release note: None 80551: sql/gcjob/gcjobnotifier: fix rare panic r=ajwerner a=ajwerner If a notifier is added before the initial system config, it can result in a crash. This may be more common in 22.1, where the initial config takes longer to be populated. Fixes #77425 Release note (bug fix): Fixes a rare crash which can occur when restarting a node after dropping tables. Co-authored-by: Nathan VanBenschoten <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Aayush Shah <[email protected]> Co-authored-by: Ricky Stewart <[email protected]> Co-authored-by: Andrew Werner <[email protected]>
- Loading branch information
Showing
46 changed files
with
2,990 additions
and
211 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.