You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
152353: opt: index accelerate LTREE with ancestry operators, @> and <@ r=paulniziolek a=paulniziolek
#### opt: index accelerate `@>` operator for ltree
The `@>` operator is accelerated by restricting the spans to be the union of
equality spans for all sub-ltrees rooted at ''. For example, a query with
predicate `WHERE a `@>` 'A.B'` would create spans [/'' - /''], [/'A' - /'A'],
[/'A.B' - /'A.B'].
Informs: #44657
Epic: CRDB-148
Release note (performance improvement): LTREE is now index accelerated with the
``@>`` operator.
#### opt: index accelerate <@ operator for ltree
The <@ is index accelerated by restricting the span of key-encoded ltrees to be
between a given ltree and the ltree with an incremented last label. For
example, a query with predicate `WHERE a <@ 'A.B'` would create the span
[/'A.B' - /'A.C'].
Informs: #44657
Epic: CRDB-148
Release note (performance improvement): LTREE is now index accelerated with the
`<`@`` operator.
152523: sql: harden recent fix to deleteRange r=yuzefovich a=yuzefovich
In recently merged 59a28ec we fixed how we count "rows affected" by the deleteRangeNode, which was done by maintaining "cur row prefix" across BatchRequests. AI-generated code review pointed out that we can alias the memory of now-old BatchRequest while processing the response to the new one. Although I don't think it can lead to problems (since we shouldn't be modifying the BatchRequest's or BatchResponse's keys - which is verified via `GRPCTransportFactory` "race" variant), it seems prudent that we make a copy of the row prefix (among other benefits, this might allow for the old keys to be GCed sooner).
Epic: None
Release note: None
Co-authored-by: Paul Niziolek <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments