postgres=# select * from sessions where video_id = 'LjiU6kB6izw';
Logical decoding of archived WALs
Use an archive-fed standby as a logical-decoding engine.
session summary
The session began by testing whether Postgres 16's logical decoding on a standby could turn an archive-fed recovery instance into a detached decoding engine. The group concluded a full server is the practical first implementation because it supplies catalog snapshots and output plugins; the missing behavior is to pause replay when it would invalidate a slot and continue when consumption advances. They also identified broader uses: per-record WAL verification, recovery debugging, and filtered, PII-free staging streams.
timecodes
- Why decode archived WAL away from production
- Using an archive-fed standby as the decoder
- Standalone WAL tool versus a full Postgres server
- Slot conflicts and the need to pause replay
- Choosing a recovery mode driven by consumption
- Function-based recovery targets
- Stepping through WAL for correctness testing
- Filtered, PII-free staging from archived WAL