-
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
110102: sql: do not generate index recs when they are not shown r=mgartner a=mgartner While diagnosing a bug with index recommendations, I noticed that index recommendations were being generated for `EXPLAIN` modes that never show the recommendations: `OPT`, `DDL`, and `VEC`. This commit eliminates that unnecessary computation. Epic: None Release note: None 110201: roachpb: add lock durability info to Get/Scan/ReverseScan requests r=nvanbenschoten a=arulajmani This patch adds lock durability information to Get, Scan, and ReverseScan requests. This field is only ever meaningful in conjunction with a locking strength that's not lock.None. By default, all locking requests ask for best-effort locks. This preserves the mixed version story between 23.1 <-> 23.2 nodes. However, transactions that need them for correctness (read: read committed), will now have the option to ask for guranteed durability locks. These will then correspond to replicated locks. Note that the field here is named in terms of durability guarantees, and not the specific implementation detail we'll use to provide this -- this is intentional. It allows us to offer a different kind of durable locks in the future, for example schemes that selectively replicate locks because they have buy-in from the both the kvserver and kvclient, in conjunction with some scheme to verify locks at commit time. Informs #109672 Release note: None 110238: skip: add Unimplemented skip reason r=knz a=stevendanna Some test cases are skipped because we intend to work on a feature in the future and have written the test to show the desired end-state once written. Having a special method for this case allows us to semantically distinguish these kinds of skips from skips that are the results of bugs or unknown issues. Epic: none Release note: None 110389: concurrency: correctly defer to higher lock strength during dup access r=nvanbenschoten a=arulajmani Burns down a TODO which only did so for lock.None lock strength. This was left over from a time when the lock table only expected lock.None and lock.Exclusive lock strengths. When a key is being accessed with more than one lock strengths in a batch, we want to defer conflict resolution to the higher lock strength, as the lower lock strength access has sufficient protection from it. This means that if a lock table scan is resumed somewhere in the middle, and we've already checked for conflicts at the key before, we can simply ignore it and move on. Note that it doesn't matter if there is a conflict at the key -- we won't proceed to evaluation before coming back to this key, while holding latches and restarting our scan from the begining, so it'll be caught then. Epic: none Release note: None 110391: ui: use MAX downsampler for sql connection rate r=sean- a=dhartunian Epic: None Release note (ui change): The "SQL Connection Rate" metric on the SQL Dashboard is downsampled using the MAX function instead of SUM. This improves situations where zooming out would cause the connection rate to increase for downsampled data. 110429: ui: fix generated `DROP INDEX` statement on table details page r=zachlite a=zachlite This commit does two things: 1. Fixes the generated `DROP INDEX` statement by considering already quoted fully-qualified names. 2. Adds unit tests for the `QuoteIdentifier` utility to clarify its intended usage and limitations. Epic: none Release note (bug fix): Fixed a UI issue where the DROP_UNUSED index recommendations produced by the table details page produced an invalid `DROP INDEX` statement. Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Arul Ajmani <[email protected]> Co-authored-by: Steven Danna <[email protected]> Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Zach Lite <[email protected]>
- Loading branch information
Showing
32 changed files
with
337 additions
and
191 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
Oops, something went wrong.