pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedNo backup history file found
2+ messages / 2 participants
[nested] [flat]
* No backup history file found
@ 2022-08-26 09:05 PG Doc comments form <noreply@postgresql.org>
2022-08-30 20:36 ` Re: No backup history file found Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 2+ messages in thread
From: PG Doc comments form @ 2022-08-26 09:05 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: eugene.pliskin@gmail.com
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: No backup history file found
2022-08-26 09:05 No backup history file found PG Doc comments form <noreply@postgresql.org>
@ 2022-08-30 20:36 ` Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 2+ messages in thread
From: Bruce Momjian @ 2022-08-30 20:36 UTC (permalink / raw)
To: eugene.pliskin@gmail.com; pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-08-30 20:36 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-08-26 09:05 No backup history file found PG Doc comments form <noreply@postgresql.org>
2022-08-30 20:36 ` Bruce Momjian <bruce@momjian.us>
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