Live data from Hacker News

Introducing WAL-G: Faster Disaster Recovery for Postgres

citusdata.com

1–10 of 66 posts

Re: Introducing WAL-G: Faster Disaster Recovery for Postgres

#3
I've used WAL-E (the predecessor of this) for backing up Postgres's DB for years and it's been a very pleasant experience. From what I've read so far this looks like it's superior in every way. Lower resource usage, faster operation, and the switch to Go for WAL-G (v.s. Python for WAL-E) means no more mucking with Python versions either.

Great job to everybody that's working on this. I'm looking forward to trying it out.

Re: Introducing WAL-G: Faster Disaster Recovery for Postgres

#4
post #2

Hello everyone, I'm the primary author for WAL-G and would be happy to answer any questions.

Thanks for making this! To someone who's unfamiliar with Postgres tooling, what's the difference between WAL-G and Barman? What're the advantages of using one over the other?

Re: Introducing WAL-G: Faster Disaster Recovery for Postgres

#5
post #2

Hello everyone, I'm the primary author for WAL-G and would be happy to answer any questions.

Thanks for making this! To someone who's unfamiliar with Postgres tooling, what's the difference between WAL-G and Barman? What're the advantages of using one over the other?

I was kafkes's guide on this project, and the WAL-E author and maintainer...

I'd say the differences between WAL-G and Barman are similar to WAL-E and Barman, which comes up relatively frequently. https://news.ycombinator.com/item?id=13573481

In summary, WAL-E is simpler program all around that focuses on cloud storage, barman does more around inventories of backups and file-based backups and configuring Postgres. There are integrative downsides to its span. WAL-E also happens to predate Barman.

Re: Introducing WAL-G: Faster Disaster Recovery for Postgres

#8
post #3

I've used WAL-E (the predecessor of this) for backing up Postgres's DB for years and it's been a very pleasant experience. From what I've read so far this looks like it's superior in every way. Lower resource usage, faster operation, and the switch to Go for WAL-G (v.s. Python for WAL-E) means no more mucking with Python versions either. Great job to everybody that's working on this. I'm looking forward to trying it…

Every time I saw that mentioned, my mind goes to the movie. https://g.co/kgs/d8G9u5

Re: Introducing WAL-G: Faster Disaster Recovery for Postgres

#10
post #2

Hello everyone, I'm the primary author for WAL-G and would be happy to answer any questions.

Seriously awesome work on this! I was expecting some solid improvement when I heard you were rewriting this in Go, but this is beyond what I could have expected. 7x improvement on high end instance types!

Also, what an impressive project to have on the resume as a college intern. I don't think many interns get to tackle something so meaningful.

Post reply on HN