Re: wal-g (https://github.com/wal-g/wal-g) reliability - Mailing list pgsql-admin

From Ron
Subject Re: wal-g (https://github.com/wal-g/wal-g) reliability
Date
Msg-id f78b01cf-de0f-be5b-0d73-cb931f6c7251@gmail.com
Whole thread Raw
In response to Re: wal-g (https://github.com/wal-g/wal-g) reliability  (Stephen Frost <sfrost@snowman.net>)
List 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.

pgsql-admin by date:

Previous
From: Stephen Frost
Date:
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
Next
From: Victor Sudakov
Date:
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability