From: | Victor Sudakov <vas(at)sibptus(dot)ru> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: wal-g (https://github.com/wal-g/wal-g) reliability |
Date: | 2021-02-09 11:07:52 |
Message-ID: | YCJtCOi+M7F1aN04@admin.sibptus.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Andrey Borodin wrote:
>
>
> > 9 февр. 2021 г., в 15:12, Victor Sudakov <vas(at)sibptus(dot)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(at)fidonet http://vas.tomsk.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2021-02-09 17:46:36 | Re: wal-g (https://github.com/wal-g/wal-g) reliability |
Previous Message | Andrey Borodin | 2021-02-09 10:22:13 | Re: wal-g (https://github.com/wal-g/wal-g) reliability |