From: Michael Paquier <michael@paquier.xyz>
To: Gert Cuykens <gert.cuykens@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backup_manifest rename to backup_manifest.old after successful postgres start up
Date: Sat, 29 Jul 2023 11:55:41 +0900
Message-ID: <ZMR/rTPkXu9roE2t@paquier.xyz> (raw)
In-Reply-To: <CAG7ytiu+evtyGskgEj8+Vm8mwy9OBWgOmxyDbN444PCzE22E2A@mail.gmail.com>
References: <CAG7ytiu+evtyGskgEj8+Vm8mwy9OBWgOmxyDbN444PCzE22E2A@mail.gmail.com>
On Tue, Jul 18, 2023 at 01:53:23AM +0200, Gert Cuykens wrote:
> Hi, suggest to automatically rename backup_manifest to backup_manifest.old
> like backup_label when postgres start up successfully because it has no use
> anymore for pg_verifybackup after postgres has been started.
Yes, I would agree with you that it is not especially useful to keep
it around once the cluster has been recovered from a base backup. It
would actually lead to various errors if attempting to run
pg_verifybackup on its data folder, for instance.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: michael@paquier.xyz, gert.cuykens@gmail.com
Subject: Re: backup_manifest rename to backup_manifest.old after successful postgres start up
In-Reply-To: <ZMR/rTPkXu9roE2t@paquier.xyz>
References: <CAG7ytiu+evtyGskgEj8+Vm8mwy9OBWgOmxyDbN444PCzE22E2A@mail.gmail.com> <ZMR/rTPkXu9roE2t@paquier.xyz>
* 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