mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-16 09:52:54 +00:00
Problem We would like to handle the tightening of unexpected WAL record types, but don't know if this happens in the field. Summary of Changes Add a rate-limited WAL log on such events. The rate limiting is to play it safe and guard against spewing in prod.
20 lines
415 B
TOML
20 lines
415 B
TOML
[package]
|
|
name = "wal_decoder"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
|
|
[features]
|
|
testing = []
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
bytes.workspace = true
|
|
once_cell.workspace = true
|
|
pageserver_api.workspace = true
|
|
postgres_ffi.workspace = true
|
|
serde.workspace = true
|
|
tracing.workspace = true
|
|
utils.workspace = true
|
|
workspace_hack = { version = "0.1", path = "../../workspace_hack" }
|