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
We've previously disallowed writing MVCC range tombstones across local
keyspace. However, this check used `keys.IsLocal()`, which simply checks
whether the key has the local prefix (`\x01`), so it was possible for
callers to use e.g. `\x00` as a start key and span the local keyspace
anyway.
This patch changes the check to ensure the start key is at or after
`keys.LocalMax`.
Release justification: bug fixes and low-risk updates to new functionality
Release note: None
0 commit comments