From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
Date: Tue, 9 Feb 2021 17:12:57 +0700
Message-ID: <YCJgKTHY2pbPnWZj@admin.sibptus.ru> (raw)
In-Reply-To: <7377779A-6763-415E-B132-0998957626FA@yandex-team.ru>
References: <YB0VuB8RJAKvTI6+@admin.sibptus.ru>
<CANNMO++t7hLG2Uk-M61ohXGNhBYszSPL8vn=zP09tcRv15QB4A@mail.gmail.com>
<YCDKyYzrv4HQZz9t@admin.sibptus.ru>
<7377779A-6763-415E-B132-0998957626FA@yandex-team.ru>
Andrey Borodin wrote:
>
> Thanks, Nikolay, I'm pleased to read good things about project I maintain.
>
> I'll add some Pros and Cons of WAL-G from my side.
>
> Pros:
> WAL-G is very efficient. At Y.Cloud we have few petabytes of PG, 12K+ of hosts. Each cluster is backuped every night (with deltas) and network cost us real moneys (our datacenters are in different countries BTW). This is our data and we highly value each byte. So we aim to make WAL-G 100% safe and tested.
> WAL-G works with PG, MySQL, MongoDB, FDB and MS SQL Server. And almost any storage (cloud, file system or scp). WAL-G does not need any extra space near database.
>
> Cons:
> We are not PG vendor. We contribute to PG ecosystem to make our systems better and reduce risks for Yandex.Cloud customers. You are not expected to buy commercial support for WAL-G from us directly. Though community behind WAL-G is big enough and there are many hackers who can implement feature you want.
> And as a result, docs are not very detailed. We would appreciate any docs enhancements.
I'm considering WAL-G now, not as a backup solution per se, but as an
advanced WAL archiver which can:
1. Upload/download WALs directly to S3
2. Verify WALs integrity (a very nice feature, but I think does not work
if there are no backups)
3. Prevent WAL overwrite (does it work?)
4. Concurrently download WALs to speed up recovery.
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: vas@sibptus.ru, pgsql-admin@lists.postgresql.org
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
In-Reply-To: <YCJgKTHY2pbPnWZj@admin.sibptus.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox