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 02:47:02 |
Message-ID: | YCH3pqahVncfF2O2@admin.sibptus.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Stephen Frost wrote:
> >
> > 2. Is there a `wal-g backup-fetch` option for truly self-sufficient
> > restoration?
>
> Interesting that you ask this! I say that because it's actually a case
> that pgbackrest contemplated and explicitly added support for-
> specifically, if you set --archive-copy (or archive-copy=true) and
> disable compression (or decompress everything before you start PG), then
> you can just start PG from the backup and it'll perform the necessary
> recovery from the WAL and start up. We considered this an interesting
> use-case and used it extensively and have maintained support for it.
Well, the release I've downloaded from https://github.com/wal-g/wal-g/releases
does not seem to have the --archive-copy option.
>
> All that said, of course, this limits the ability to do typical PITR,
Why? If you configure recovery_target_time and restore_command, it's all
the same, isn't it? No matter if you have WAL archives in pg_wal, but
it's better to have them.
> but at least it gives you a consistent backup which you can start PG
> from.
>
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49(at)fidonet http://vas.tomsk.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2021-02-09 08:25:05 | Re: wal-g (https://github.com/wal-g/wal-g) reliability |
Previous Message | Ron | 2021-02-08 21:41:20 | Re: wal-g (https://github.com/wal-g/wal-g) reliability |