-
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
53529: sql: fix limits on virtual index scans r=jordanlewis a=jordanlewis Previously, virtual indexes mis-reported their key columns as containing only their index key. Virtual indexes always need to contain the dummy PK column since they're not guaranteed to be unique. This caused some broken behavior like limits not working properly in some cases. Fixes #53522 Release note (bug fix): virtual index scans respect limits properly as they did in 20.1 and prior. Release justification: bug fix to new functionality 53572: roachtest: Bump up node/SSD size for clearrange roachtests r=itsbilal a=itsbilal For the clearrange/* roachtests, the instances we spun up on aws (c5d.xlarge) had 4x less local ssd storage space as the ones we spun up on gce. This extra headroom made a pretty significant difference, as the bigbank workload import would easily exceed the ~900gb usable capacity on a 10x c5d.xlarge node cluster (it was observed to take around 1.9TB on GCE). This change bumps up the instance size indirectly, by requiring more CPUs which is how the instance type is determined. A related, though less pressing change, is to allow for increased concurrency in AddSSTable requests to make the import go faster. Release justification: Roachtest change, doesn't affect cockroach binary Release note: None. 53585: coldata: optimize copying nulls in a common case r=yuzefovich a=yuzefovich Whenever we're copying `coldata.Vec`s, we need to copy the nulls vectors as well. Often, we would be copying the nulls vectors in such a manner that the shifts within nulls bitmaps would be the same. Such observation allows us to optimize the copying behavior (previously, we would be checking and setting every null value one at a time), but now we will do a more efficient copy for the largest central part of the range to copy and handle the "head" and the "tail" of the range separately. This gives us a nice speedup (e.g. on a quick projection operator benchmark I see 2x improvement in the throughput). Release justification: low risk, high benefit change. Release note: None 53588: coldata,sql: remove some todos r=yuzefovich a=yuzefovich This commit removes several TODOs that I have prototyped addressing and decided to abandon the prototypes, namely: - checking whether `coldata.BatchSize()` atomic has influence on performance (the benchmarks and TPCH queries showed that the impact is negligible if any) - tuning default batch size (I did that a while ago, and the best batch size according tpchvec/bench was 1280, barely better than current 1024 which is a lot nicer number) - pooling allocations of `execFactory` objects (this showed some improvement on one workload and a regression on another). Release justification: non-production code changes. Release note: None 53608: scripts: add --hide-crdb-folk option to release-notes r=jordanlewis a=jordanlewis Add an option to the release notes script that generates all of the commits made by non-crdb people over the last time duration. Release note: None Release justification: non-code change 53645: builtins: implement ST_Collect aggregate r=otan a=erikgrinaker Also contains `geomfn.Collect()` for the binary version of `ST_Collect` (#48902), but the builtin could not be implemented since it cannot have the same name as an aggregate function. The code is left behind for when this constraint is lifted, but I'm happy to remove it entirely if preferred. The aggregation optimistically uses a multitype, but once it encounters an incompatible geometry it converts the existing multitype into a collection, using additional memory and CPU time - ideas for how to avoid this are welcome. Test coverage is less than great, but I could not see any existing convention for comprehensive testing of aggregate functions. Release justification: low risk, high benefit changes to existing functionality Release note (sql change): Implement the geometry aggregate builtin ST_Collect. Closes #48903. 53674: sql: de-experimentalize user defined schemas r=rohany a=rohany Release justification: low-risk update to new functionality Release note (sql change): De-experimentalize user defined schemas. 53681: stats: fix and unskip flaky test TestCreateStatsProgress r=rytaft a=rytaft Release justification: non-production code changes This commit fixes the flaky test `TestCreateStatsProgress` and unskips it. `TestCreateStatsProgress` was flaky because of the recent changes to the stats cache, which removed the guarantee that fresh stats would be available in the cache immediately after stats creation. This commit fixes the issue by explicitly invalidating the stats cache before the part of `TestCreateStatsProgress` that expects certain stats to be present. Fixes #52782 Release note: None 53682: sql: volatility for casts between tuples r=RaduBerinde a=RaduBerinde #### sql: volatility for casts between tuples We were missing code for determining volatility when casting between tuples. This is because there is no way to express such a cast directly in SQL, but there are cases where these casts appear implicitly (such as a conditional). This change adds the missing logic and a corresponding test. Fixes #53395. Release justification: low-risk fix of regression. Release note (bug fix): fixed an internal error related to casts between tuples. Co-authored-by: Jordan Lewis <[email protected]> Co-authored-by: Bilal Akhtar <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Erik Grinaker <[email protected]> Co-authored-by: Rohan Yadav <[email protected]> Co-authored-by: Rebecca Taft <[email protected]> Co-authored-by: Radu Berinde <[email protected]>
- Loading branch information
Showing
50 changed files
with
984 additions
and
566 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.