Inject disk exhaustion locally, observe write failure, and prove cleanup restores durable writes.
A service reports healthy because its process is alive, while WAL writes fail with ENOSPC. Log rotation also fails, retries amplify load, and deleting one file does not prove durable writes resumed.
Bounded local fault injection
mkdir -p ./disk-fixture
dd if=/dev/zero of=./disk-fixture/filler bs=1M count=900
# Run only inside a disposable volume with a declared size.
Inject a long read transaction and observe why a healthy process can still grow its WAL toward disk exhaustion.
Last year, on a client project, I noticed a sudden spike in disk usage on a PostgreSQL database...
PostgreSQL WAL Bloat: Why Automatic Management Is Often Insufficient? While managing a...
Database WAL Bloat: How to Overcome the Performance Trap? WAL (Write-Ahead Logging) bloat...
Build a small backup drill that catches missing WAL data and incompatible schema changes.
TL;DR Bug: Calling optimize() on a ZVec Collection that had recovered from an unclean...
