mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-11 07:22:55 +00:00
07b974480c
## Problem We wish to have high level WAL decoding logic in `wal_decoder::decoder` module. ## Summary of Changes For this we need the `Value` and `NeonWalRecord` types accessible there, so: 1. Move `Value` and `NeonWalRecord` to `pageserver::value` and `pageserver::record` respectively. 2. Get rid of `pageserver::repository` (follow up from (1)) 3. Move PG specific WAL record types to `postgres_ffi::walrecord`. In theory they could live in `wal_decoder`, but it would create a circular dependency between `wal_decoder` and `postgres_ffi`. Long term it makes sense for those types to be PG version specific, so that will work out nicely. 4. Move higher level WAL record types (to be ingested by pageserver) into `wal_decoder::models` Related: https://github.com/neondatabase/neon/issues/9335 Epic: https://github.com/neondatabase/neon/issues/9329
16 lines
259 B
Rust
16 lines
259 B
Rust
#![deny(unsafe_code)]
|
|
#![deny(clippy::undocumented_unsafe_blocks)]
|
|
|
|
pub mod controller_api;
|
|
pub mod key;
|
|
pub mod keyspace;
|
|
pub mod models;
|
|
pub mod record;
|
|
pub mod reltag;
|
|
pub mod shard;
|
|
/// Public API types
|
|
pub mod upcall_api;
|
|
pub mod value;
|
|
|
|
pub mod config;
|