Vlad Lazar 665369c439 wal_decoder: fix compact key protobuf encoding (#10074) ...

## Problem

Protobuf doesn't support 128 bit integers, so we encode the keys as two
64 bit integers. Issue is that when we split the 128 bit compact key we
use signed 64 bit integers to represent the two halves. This may result
in a negative lower half when relnode is larger than `0x00800000`. When
we convert the lower half to an i128 we get a negative `CompactKey`.

## Summary of Changes

Use unsigned integers when encoding into Protobuf.

## Deployment

* Prod: We disabled the interpreted proto, so no compat concerns.
* Staging: Disable the interpreted proto, do one release, and then
release the fixed version.
We do this because a negative int32 will convert to a large uint32 value
and could give
a key in the actual pageserver space. In production we would around this
by adding new
fields to the proto and deprecating the old ones, but we can make our
lives easy here.
* Pre-prod: Same as staging

2024-12-11 12:35:02 +00:00

..

src

wal_decoder: fix compact key protobuf encoding (#10074)

2024-12-11 12:35:02 +00:00

Cargo.toml

fast imports: initial Importer and Storage changes (#9218)

2024-11-22 22:47:06 +00:00