Vlad Lazar 0d9a45a475 safekeeper: invalidate start of interpreted batch on reader resets (#10951) ...

## Problem

The interpreted WAL reader tracks the start of the current logical
batch.
This needs to be invalidated when the reader is reset.

This bug caused a couple of WAL gap alerts in staging.

## Summary of changes

* Refactor to make it possible to write a reproducer
* Add repro unit test
* Fix by resetting the start with the reader

Related https://github.com/neondatabase/cloud/issues/23935

2025-02-25 10:21:35 +00:00

..

benches

pageserver,safekeeper: increase heap profiling frequency to 2 MB (#10362)

2025-01-13 09:44:59 +00:00

client

storcon: sk heartbeat fixes (#10891)

2025-02-19 16:57:11 +00:00

spec

TLA+ spec for safekeeper membership change (#9966)

2025-01-09 12:26:17 +00:00

src

safekeeper: invalidate start of interpreted batch on reader resets (#10951)

2025-02-25 10:21:35 +00:00

tests

Add START_WAL_PUSH proto_version and allow_timeline_creation options. (#10406)

2025-01-16 08:01:19 +00:00

Cargo.toml

Remove unnecessary dependencies to synchronous 'postgres' crate (#10938)

2025-02-24 09:40:25 +00:00