Re: pgbackrest - question about restoring cluster to a new cluster on same server

From: David Steele <david(at)pgmasters(dot)net>
To: Jerry Sievers <gsievers19(at)comcast(dot)net>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pgbackrest - question about restoring cluster to a new cluster on same server
Date: 2019-09-19 02:30:40
Message-ID: 85a8b7ef-c1c7-4f62-028d-dc814f665f5b@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/18/19 10:18 PM, Jerry Sievers wrote:
> David Steele <david(at)pgmasters(dot)net> writes:
>
>> This is not an issue unless you seriously game the system. When a
>
> And/or your recovery system is running archive_mode=always :-)
>
> I don't know how popular that setting value is but that plus an
> identical archive_command as the origin... duplicate archival with
> whatever consequences.
>
> Disclaimer: I don't know if pgbackrest guards against such a
> configuration.

We current disallow archive_mode=always because the locking issues are
complex. Also, standbys will not always push WAL which is binary
identical to the primary (even though they are logically the same) so it
can be really tricky to tell who is authoritative.

We have plans in this area but they are currently on the back-burner.

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ken Tanzer 2019-09-19 04:43:25 Re: PostgreSQL License
Previous Message Jerry Sievers 2019-09-19 02:18:24 Re: pgbackrest - question about restoring cluster to a new cluster on same server