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
fix(catalog): use scan_prefix instead of 0xFF-bounded range scans
Prefix scans over catalog rows built their end bound by appending a
single 0xFF byte to the start key. For a realm or segment id whose
first byte is itself 0xFF, that end bound sorts before (or equal to)
some in-range keys, silently dropping rows from segment listing,
stats, and rekey migration. One such migration failed with an
unverifiable-header corruption. Replace every appended-sentinel range
scan with scan_prefix, which bounds correctly regardless of key
content.
0 commit comments