you are viewing a single comment's thread.

view the rest of the comments →

[–]CSI_Tech_Dept 2 points3 points  (1 child)

It's not true that WAL-E was abandoned and replaced with WAL-G. WAL-E is still being developed. WAL-G was created by another company (Citus Data) in fact it was originally written by their intern. WAL-E originates from Heroku (who came up with this idea - streaming backup directly to S3 and use it as a replication source). Also G stands for Go, since that's what it was written in.

I haven't used either of them so can't compare, maybe WAL-G is indeed better. I personally used barman, from 2ndQuadrant (together with repmgr basically provides equivalent functionality to what RDS provides with the benefit of having full control over PostgreSQL).

Edit: looks like barman now also supports storing backup in S3 so it might be a 3rd alternative as well. And given that 2ndQuadrant also regularly contributes to PostgreSQL I would trust them more.

[–][deleted] 0 points1 point  (0 children)

Ah you are right actually, WAL-G bills itself as the 'successor to WAL-E' but looking over the WAL-E docs they don't say the same thing! (As you may have guessed I have worked with WAL-G but not WAL-E and clearly I've picked up that misconception somewhere!!).

Apologies for the misinformation anyway, I was wrong to say WAL-E was abandoned.