PostgreSQL WAL & Replication: The 380MB No-Op Update, Orphan Slots & 2 AM Disk-Full Playbook
PostgreSQL Write-Ahead Logging and replication mechanics: why a no-op UPDATE generates 380MB of WAL, replication lag causes, orphan replication slots exhausting disk, silent archive_command failures, and the 2 AM 95% disk emergency playbook.