Introducing WAL-G: Faster Disaster Recovery for Postgres

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by jfkw on Friday August 18, 2017 @03:34PM (#15049089)

Will WAL-G eventually support the same archive targets as WAL-E (S3 and work-alikes, Azure Blob Store, Google Storage, Swift, File System)?

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by fdr on Friday August 18, 2017 @04:37PM (#15049527)

As I'm probably the steward on this going forward: unknown. I don't intend to implement them unless I need them. Would I take a patch with good coverage that implemented those.

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by boulos on Saturday August 19, 2017 @04:51PM (#15055525)

Would you be willing to own the abstraction for multiple backends? The code is currently only a bit hardcoded to S3/AWS, but I assume most of the "work" will be discussing how to abstract different transports, exponential backoff, resumable uploads, and so on.

Fwiw, the GCS client for go (import "cloud.google.com/go/storage") is very straightforward. Though as others have pointed out, it might be worthwhile to just try to use minio-go if you want to gain Ceph as well.

Disclosure: I work on Google Cloud (and if the way is paved, we will contribute here; seems like a great project)

[ Parent | on HN ]