FRESH

Hacker News

WAL-RUS: a Rust Rewrite of WAL-G for PostgreSQL Backups

132 points by saisrirampur

by nasretdinov

1 subcomments

I must say I'm quite pleased to see how well Go version works. It does only use 1.5x the CPU and (predictably) much more RAM/VRAM, but not a crazy amount either (the expected increase is 2x).
Of course you can write a more optimal version in C / C++ / Zig / Rust, but at the same time Go is much easier to write and you don't pay for the convenience with an absurd performance loss like in Python or PHP

by TOMDM

0 subcomment

PostgreSQL WAL-RUS, no relation to PostgreSQL WALRUS https://github.com/supabase/walrus

by whitepoplar

1 subcomments

As someone who only has a cursory knowledge of Postgres backup systems, how does this compare to something like pgBackRest? When would someone reach for one over the other?

by caffeinated_me

1 subcomments

Do you have any benchmarks with a mix of long open transactions and short ones? I've struggled a lot with WAL-E in the past there, and am curious if that changes here.

by westurner

0 subcomment

How to Design an index layer for postgres WAL-G backups to make a paging VFS like sqlite-http-vfs for pglite in WASM?

by dionian

0 subcomment

by valentynkit

1 subcomments

Quick one on the benchmark: was the 2.8GB peak virtual or resident? Go reserves a large virtual arena it mostly never faults in, so RSS tends to be a fraction of the virtual peak, and if Postgres headroom was getting squeezed off the virtual number you were sizing against memory the kernel never actually charges for.

by cipherself

0 subcomment

The article’s distinction about memory is a bit too simplified. Virtual memory is address space mapped or reserved by the process. RSS is resident physical pages, not necessarily “actively used.”. RSS also overcounts shared memory, which is why PSS/USS matter.