Is wal2 considered stable enough to be used in production scenarios? It looks like the branch is kept well up-to-date with the main branch. Are there any plans to make it into an official feature? Motivation: our database has an uninterrupted stream of small write operations with relatively strict latency constraints. We want to run in WAL mode, but WAL checkpoints exceed these latency constraints. When WAL checkpoints are moved to a background thread, as the documentation suggests, we run into the ever-growing-wal-file problem. The wal2 branch solves exactly this problem (we can confirm it works). Other solutions like moving all writes to a background thread or buffering the incoming writes mean we lose a lot of the database's nice features. Thanks.