📄️ Daemon Modes
pgrwl running in receive mode
📄️ Design Notes
pgrwl is designed to always stream WAL data to the local filesystem first. This design ensures durability and
📄️ Disaster Recovery Use Cases
The full process may look like this (a typical, rough, and simplified example):
📄️ Durability & fsync
- After each WAL segment is written, an fsync is performed on the currently open WAL file to ensure durability.
📄️ Architecture
The architecture section explains why pgrwl writes to the local filesystem first, how durability is preserved with fsync, and why streaming replication is used instead of relying only on archive_command.
📄️ Why Not archive_command?
There’s a significant difference between using archive_command and archiving WAL files via the streaming replication