diff options
| author | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:11 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:11 +0900 |
| commit | 677357047b9c920e351b73d9670a813fcdc6801b (patch) | |
| tree | ddcba2ba5d0c255e9b208e327e96ba1686708f51 | |
| parent | d6ca789dde70f2c323b79559b8ce0746ddf7a48d (diff) | |
doc: Clarify how to generate backup files with non-exclusive backups
The current instructions describing how to write the backup_label and
tablespace_map files are confusing. For example, opening a file in text
mode on Windows and copy-pasting the file's contents would result in a
failure at recovery because of the extra CRLF characters generated. The
documentation was not stating that clearly, and per discussion this is
not considered as a supported scenario.
This commit extends a bit the documentation to mention that it may be
required to open the file in binary mode before writing its data.
Reported-by: Wang Shenhao
Author: David Steele
Reviewed-by: Andrew Dunstan, Magnus Hagander
Discussion: https://postgr.es/m/8373f61426074f2cb6be92e02f838389@G08CNEXMBPEKD06.g08.fujitsu.local
Backpatch-through: 9.6
| -rw-r--r-- | doc/src/sgml/backup.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 120d58652fb..f0995a46cf6 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -904,7 +904,8 @@ SELECT * FROM pg_stop_backup(false, true); <filename>backup_label</filename> in the root directory of the backup. The third field should be written to a file named <filename>tablespace_map</filename> unless the field is empty. These files are - vital to the backup working, and must be written without modification. + vital to the backup working and must be written byte for byte without + modification, which may require opening the file in binary mode. </para> </listitem> <listitem> |