Rust rewrites keep coming, now for PostgreSQL backup tooling

WAL-RUS, a Rust rewrite of WAL-G for PostgreSQL backups, landed on HN today and got substantive engagement from people who clearly run Postgres in production. The discussion was technical: questions about benchmark methodology, behavior under long open transactions, memory usage comparisons between the Rust and Go versions. The Go version of WAL-G uses 1.5x the CPU of the Rust version and more RAM, but not catastrophically more.

This is one data point in a longer trend. Rust is steadily absorbing performance-critical infrastructure tooling, particularly in the database and networking layers. The WAL-RUS thread is notable because the benchmarks are being scrutinized seriously, not cheerled, which suggests the Rust-for-infrastructure wave is maturing past hype into actual engineering evaluation.

The counterpoint: commenters noted that the Go version works well enough for most use cases, and switching backup infrastructure is not a casual decision. The performance gains from Rust are real but not always the bottleneck.