From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
Date: Mon, 8 Feb 2021 15:41:20 -0600
Message-ID: <f78b01cf-de0f-be5b-0d73-cb931f6c7251@gmail.com> (raw)
In-Reply-To: <20210208212840.GW27507@tamriel.snowman.net>
References: <YB0VuB8RJAKvTI6+@admin.sibptus.ru>
<CANNMO++t7hLG2Uk-M61ohXGNhBYszSPL8vn=zP09tcRv15QB4A@mail.gmail.com>
<YCDKyYzrv4HQZz9t@admin.sibptus.ru>
<20210208212840.GW27507@tamriel.snowman.net>
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.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability
In-Reply-To: <f78b01cf-de0f-be5b-0d73-cb931f6c7251@gmail.com>
* 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