-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
118603: *: retire multi tenant VTeam attributes r=yuzefovich a=yuzefovich **: remove all mentions of T-multitenant** Release note: None **roachtest: reassign ownership from MultiTenant to DisasterRecovery** This commit reassigns ownership of the following roachtests: - `acceptance/multitenant/` - `multitenant/shared-process/basic` - `multitenant-upgrade` to Disaster Recovery team (which is temporary until the Shared Services team if staffed). Release note: None **CODEOWNERS: remove cockroachdb/multi-tenant** This commit removes all mentions of cockroachdb/multi-tenant in favor of cockroachdb/server-prs. Release note: None Epic: None 119602: sql: reduce indexed variable allocations r=mgartner a=mgartner #### execinfrapb: remove unnecessary DefaultIntSize parse option When `execinfrapb.Expression`s are serialized, references to integer types are always formatted unambiguously with the `tree.FmtCheckEquivalence` flag as `INT2`, `INT4`, or `INT8`, and never as `INT`. Therefore, there is never a need to disambiguate the meaning of `INT` based on the `default_int_size` session setting. This allows simplification of the deserialization logic. Release note: None #### execinfrapb: remove unnecessary check for aggregates This commit removes some logic in `execinfrapb` that asserted that expressions being deserialized do not contain aggregate functions. This logics appears to be vestigial that is no longer required, though I was unable to pinpoint the original motivation behind it. This type of semantic analysis should now be performed during optimization-time, so I see no reason for it to remain. This logic was the last remaining user of the `isAggregateVisitor` so it has been removed. Release note: None #### execinfrapb: do not use tree.IndexedVarHelper Previously, a `tree.IndexedVarHelper` was used to "rebind" indexed variables in expressions deserialized in `execinfrapb`. The only real function of this rebinding was to assign types to indexed variables so that they could be type-checked. However, this was an unnecessary step because the type checker can already determine the types of indexed vars via the `IVarContainer` of the `tree.SemaContext`. The `exprHelper` type already implements `tree.IndexedVarContainer` so it was already possible to simply type-check indexed variables without rebinding them first. This reduces allocations of `tree.IndexedVarHelper`s that can be large, especially when there are many indexed variables. Release note: None #### sql/sem/tree: remove IndexedVarHelper.RebindTyped Indexed variable rebinding is no longer needed, so it has been removed. This reduces unnecessary allocations because `tree.IndexedVarHelper`s no longer need to be created to perform the rebinding. Informs #117546 Release note: None #### sql: remove extra params for IndexedVarContainer.IndexedVarEval This method signature for `IndexedVarContainer.IndexedVarEval` by removing unneeded parameters. It also removes some unnecessary calls to `Eval` on `tree.Datum`s. Release note: None #### sql: remove unnecessary invocation of makePredicate Release note: None 120677: server: include WAL failover path within the stores status r=RaduBerinde a=jbowens Expand the response from the /_status/stores endpoint to include the store's data directory and the path to the configured WAL failover secondary if configured. Close #119795. Epic: CRDB-35401 Release note: Adds a new field to the stores Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com> Co-authored-by: Marcus Gartner <marcus@cockroachlabs.com> Co-authored-by: Jackson Owens <jackson@cockroachlabs.com>
- Loading branch information
Showing
35 changed files
with
190 additions
and
399 deletions.
There are no files selected for viewing
Validating CODEOWNERS rules …
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
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.