-
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.
87261: storage: add range keys and mvccstats to gc bench r=aliher1911 a=aliher1911 Previously gc benchmarking code didn't include neither range key tombstones, nor mvcc stats calculations. This is not realistic as production always uses stats and it is a non-negligible part of the operation time. This commit adds option to enable stats calculation during benchmarking as well as adding underlying range key tombstone to include everything. Release justification: increasing bench coverage, non production. Release note: None 87310: sql: parse sequence name instead of using name identifier directly r=chengxiong-ruan a=chengxiong-ruan Previously, we use the sequence name identifier directly when building a function in optbuilder if a function expression use any sequences. This does work when sequence name string is qualifed because sequence name cannot be found. We need to parse the name string into a table name instead. Release note: None. Release justification: low risk bug fix. 87423: dev: if specified, dev generate bazel before other targets r=healthy-pod a=rickystewart The results of this generation can impact most of the other generation targets, so it should be done first. Release justification: Non-production code changes Release note: None Co-authored-by: Oleg Afanasyev <[email protected]> Co-authored-by: Chengxiong Ruan <[email protected]> Co-authored-by: Ricky Stewart <[email protected]>
- Loading branch information
Showing
6 changed files
with
106 additions
and
19 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