From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: eugene.pliskin@gmail.com
Subject: No backup history file found
Date: Fri, 26 Aug 2022 09:05:14 +0000
Message-ID: <166150471493.654.9349065682650784852@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/continuous-archiving.html
Description:
Chapter 26.3.2. "Making a Base Backup" states that "To make use of the
backup, you will need to keep all the WAL segment files generated during and
after the file system backup. To aid you in doing this, the base backup
process creates a backup history file that is immediately stored into the
WAL archive area. This file is named after the first WAL segment file that
you need for the file system backup. For example, if the starting WAL file
is 0000000100001234000055CD the backup history file will be named something
like 0000000100001234000055CD.007C9330.backup."
In my experience with pg_basebackup with tar format (-Ft) no backup history
file was produced. Instead I found first WAL segment name in "backup_label"
file inside of "base.tar" archive.
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, eugene.pliskin@gmail.com
Subject: Re: No backup history file found
In-Reply-To: <166150471493.654.9349065682650784852@wrigleys.postgresql.org>
* 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