Re: wal-g (https://github.com/wal-g/wal-g) reliability

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
Date: 2021-02-08 21:41:20
Message-ID: f78b01cf-de0f-be5b-0d73-cb931f6c7251@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 2/8/21 3:28 PM, Stephen Frost wrote:
[snip]
> 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.
>
> All that said, of course, this limits the ability to do typical PITR,
> but at least it gives you a consistent backup which you can start PG
> from.

In the SQL Server world, that's a COPY_ONLY backup.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Victor Sudakov 2021-02-09 02:47:02 Re: wal-g (https://github.com/wal-g/wal-g) reliability
Previous Message Stephen Frost 2021-02-08 21:28:40 Re: wal-g (https://github.com/wal-g/wal-g) reliability