Re: post-freeze damage control - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: post-freeze damage control
Date
Msg-id ZhXUYBXTWvF4OaPm@paquier.xyz
Whole thread Raw
In response to Re: post-freeze damage control  (David Steele <david@pgmasters.net>)
Responses Re: post-freeze damage control
List pgsql-hackers
On Wed, Apr 10, 2024 at 09:29:38AM +1000, David Steele wrote:
> Even so, only keeping WAL for the last backup is a dangerous move in any
> case. Lots of things can happen to a backup (other than bugs in the
> software) so keeping WAL back to the last full (or for all backups) is
> always an excellent idea.

Yeah, that's an excellent practive, but is why I'm less worried for
this feature.  The docs at [1] caution about "not to remove earlier
backups if they might be needed when restoring later incremental
backups".  Like Alvaro said, should we insist a bit more about the WAL
retention part in this section of the docs, down to the last full
backup?

[1]: https://www.postgresql.org/docs/devel/continuous-archiving.html#BACKUP-INCREMENTAL-BACKUP
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Speed up clean meson builds by ~25%
Next
From: David Rowley
Date:
Subject: Re: Fixup some StringInfo usages