From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgbackrest restore to new location? |
Date: | 2019-09-18 10:53:51 |
Message-ID: | 5c7420d6-ad30-7b09-516a-284b0659782b@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/17/19 10:03 PM, Stephen Frost wrote:
>
> That said- it brings up a pretty serious issue that should be discussed,
> and that's nuking this:
>
> HINT: If you are not restoring from a backup, try removing the file ".../backup_label".
>
> That hint is absolutely wrong these days when many tools have been
> updated to use the non-exclusive backup method and it just ends up
> getting people into trouble and, worse, can result in them having
> corrupted clusters.
>
> I'll get a patch into the next commitfest to remove it. The exclusive
> method has been deprecated for quite a few releases and we should stop
> giving bad advice on the assumption that people are using it.
We updated the error message and hints in c900c152, but it was not
back-patched.
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-09-18 11:44:47 | Re: pgbackrest restore to new location? |
Previous Message | Marco Ippolito | 2019-09-18 10:44:20 | Re: Installed PostgreSQL-11 in Ubuntu 18.04.02 Server Edition: No existing local cluster is suitable as a default target |