Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 7f03a79

Browse files
committed
Stress that backup_label file is critical in the docs.
It is surprisingly common mistake to leave out backup_label file from a base backup. Say more explicitly that it must be included. Jeff Janes, with minor rewording by me.
1 parent 817a894 commit 7f03a79

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

doc/src/sgml/backup.sgml

+7-4
Original file line numberDiff line numberDiff line change
@@ -826,7 +826,8 @@ SELECT pg_start_backup('label');
826826
<function>pg_start_backup</> creates a <firstterm>backup label</> file,
827827
called <filename>backup_label</>, in the cluster directory with
828828
information about your backup, including the start time and label
829-
string.
829+
string. The file is critical to the integrity of the backup, should
830+
you need to restore from it.
830831
</para>
831832

832833
<para>
@@ -945,9 +946,11 @@ SELECT pg_stop_backup();
945946
The backup label file includes the label string you gave to
946947
<function>pg_start_backup</>, as well as the time at which
947948
<function>pg_start_backup</> was run, and the name of the starting WAL
948-
file. In case of confusion it is
949-
therefore possible to look inside a backup dump file and determine
950-
exactly which backup session the dump file came from.
949+
file. In case of confusion it is therefore possible to look inside a
950+
backup dump file and determine exactly which backup session the dump file
951+
came from. However, this file is not merely for your information; its
952+
presence and contents are critical to the proper operation of the system's
953+
recovery process.
951954
</para>
952955

953956
<para>

0 commit comments

Comments
 (0)