Date: Tue, 30 Aug 2022 16:36:46 -0400
From: Bruce Momjian <bruce@momjian.us>
To: eugene.pliskin@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: No backup history file found
Message-ID: <Yw503h8nLrJsz9Ek@momjian.us>
References: <166150471493.654.9349065682650784852@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <166150471493.654.9349065682650784852@wrigleys.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/Yw503h8nLrJsz9Ek%40momjian.us>
Precedence: bulk

On Fri, Aug 26, 2022 at 09:05:14AM +0000, PG Doc comments form wrote:
> 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.

Well, what happens is the the "backup_label" file is created in the WAL
directory and that file gets backed up during the file system backup. 
That file will appear in the backup, like in the tar file.  Can that
text be improved?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson