Vlad Lazar 411c3aa0d6 pageserver: lift decoding and interpreting of wal into wal_decoder (#9524) ...

## Problem

Decoding and ingestion are still coupled in `pageserver::WalIngest`.

## Summary of changes

A new type is added to `wal_decoder::models`, InterpretedWalRecord. This
type contains everything that the pageserver requires in order to ingest
a WAL record. The highlights are the `metadata_record` which is an
optional special record type to be handled and `blocks` which stores
key, value pairs to be persisted to storage.

This type is produced by
`wal_decoder::models::InterpretedWalRecord::from_bytes` from a raw PG
wal record.

The rest of this commit separates decoding and interpretation of the PG
WAL record from its application in `WalIngest::ingest_record`.

Related: https://github.com/neondatabase/neon/issues/9335
Epic: https://github.com/neondatabase/neon/issues/9329

2024-10-31 10:47:43 +00:00

..

src

pageserver: lift decoding and interpreting of wal into wal_decoder (#9524)

2024-10-31 10:47:43 +00:00

Cargo.toml

pageserver: move things around to prepare for decoding logic (#9504)

2024-10-29 10:00:34 +00:00