From 7f03a791fa131eb20c6df07740522163d8b3c94e Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Tue, 7 May 2013 16:55:04 +0300 Subject: [PATCH] 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. --- doc/src/sgml/backup.sgml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index e444b1cde3d..ccb76d8af0a 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -826,7 +826,8 @@ SELECT pg_start_backup('label'); pg_start_backup creates a backup label file, called backup_label, in the cluster directory with information about your backup, including the start time and label - string. + string. The file is critical to the integrity of the backup, should + you need to restore from it. @@ -945,9 +946,11 @@ SELECT pg_stop_backup(); The backup label file includes the label string you gave to pg_start_backup, as well as the time at which pg_start_backup was run, and the name of the starting WAL - file. In case of confusion it is - therefore possible to look inside a backup dump file and determine - exactly which backup session the dump file came from. + file. In case of confusion it is therefore possible to look inside a + backup dump file and determine exactly which backup session the dump file + came from. However, this file is not merely for your information; its + presence and contents are critical to the proper operation of the system's + recovery process.