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 18:07:52 +0700
Message-ID: <YCJtCOi+M7F1aN04@admin.sibptus.ru> (raw)
In-Reply-To: <E9DEC4D3-66CA-4F67-9481-301B9B140124@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>
<YCJgKTHY2pbPnWZj@admin.sibptus.ru>
<E9DEC4D3-66CA-4F67-9481-301B9B140124@yandex-team.ru>
Andrey Borodin wrote:
>
>
> > 9 февр. 2021 г., в 15:12, Victor Sudakov <vas@sibptus.ru> написал(а):
> >
> > I'm considering WAL-G now, not as a backup solution per se, but as an
> > advanced WAL archiver which can:
> Keep in mind that once upon a time you will have to delete WAL segments. If you just use wal-g delete you have to point our which backup to keep.
Thank you, this is an important note.
>
> > 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)
> If will not be alarmed if WALs before backup are missing. Though it should still analyze chains correctly.
>
> > 3. Prevent WAL overwrite (does it work?)
> I think so.
>
OK.
--
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: <YCJtCOi+M7F1aN04@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