@@ -962,10 +962,10 @@ SELECT * FROM pg_stop_backup(false, true);
962
962
The process for an exclusive backup is mostly the same as for a
963
963
non-exclusive one, but it differs in a few key steps. This type of
964
964
backup can only be taken on a primary and does not allow concurrent
965
- backups. Moreover, because it writes a backup_label file on the
966
- master , it can cause the master to fail to restart automatically after
967
- a crash. On the other hand, the erroneous removal of a backup_label
968
- file from a backup or standby is a common mistake which can result
965
+ backups. Moreover, because it creates a backup label file, as
966
+ described below , it can block automatic restart of the master server
967
+ after a crash. On the other hand, the erroneous removal of this
968
+ file from a backup or standby is a common mistake, which can result
969
969
in serious data corruption. If it is necessary to use this method,
970
970
the following steps may be used.
971
971
</para>
@@ -1025,10 +1025,10 @@ SELECT pg_start_backup('label', true);
1025
1025
</para>
1026
1026
<para>
1027
1027
As noted above, if the server crashes during the backup it may not be
1028
- possible to restart until the <literal >backup_label</literal > file has
1028
+ possible to restart until the <filename >backup_label</filename > file has
1029
1029
been manually deleted from the <envar>PGDATA</envar> directory. Note
1030
1030
that it is very important to never remove the
1031
- <literal >backup_label</literal > file when restoring a backup, because
1031
+ <filename >backup_label</filename > file when restoring a backup, because
1032
1032
this will result in corruption. Confusion about when it is appropriate
1033
1033
to remove this file is a common cause of data corruption when using this
1034
1034
method; be very certain that you remove the file only on an existing
@@ -1075,7 +1075,7 @@ SELECT pg_stop_backup();
1075
1075
lack of disk space, failure to call <function>pg_stop_backup</function>
1076
1076
will leave the server in backup mode indefinitely, causing future backups
1077
1077
to fail and increasing the risk of a restart failure during the time that
1078
- <literal >backup_label</literal > exists.
1078
+ <filename >backup_label</filename > exists.
1079
1079
</para>
1080
1080
</listitem>
1081
1081
</orderedlist>
0 commit comments