From: | Michael Banck <michael(dot)banck(at)credativ(dot)de> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: v12 and TimeLine switches and backups/restores |
Date: | 2020-07-01 20:48:04 |
Message-ID: | 5efcf684.1c69fb81.b6539.5d95@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Wed, Jul 01, 2020 at 12:12:14AM -0400, Stephen Frost wrote:
> Specifically, if you take a backup off a primary and, while that backup
> is going on, some replica is promoted and drops a .history file into the
> WAL repo, that backup is no longer able to be restored with the new
> recovery_target_timeline default.
Quick question to grasp the magnitude of this:
If a user takes a backup with pg_basebackup in streaming mode, would
that still be a problem? Or is this "only" a problem for base backups
which go through a wal archive common between primary and standby?
Michael
--
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax: +49 2166 9901-100
Email: michael(dot)banck(at)credativ(dot)de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2020-07-01 20:54:01 | Re: SQL-standard function body |
Previous Message | Bruce Momjian | 2020-07-01 20:46:42 | Re: Remove Deprecated Exclusive Backup Mode |