diff options
| author | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:28 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:28 +0900 |
| commit | cc7416f3b679decdf2d073fc35402f6e2235720e (patch) | |
| tree | ec58e3f0ee481f76c79c36136f4529c24893bc25 | |
| parent | ab88525ad29cc23f99eb615258621caadbb5127e (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 76b55433426..b7ec53a5986 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -903,7 +903,8 @@ SELECT * FROM pg_stop_backup(false); <filename>backup_label</> in the root directory of the backup. The third field should be written to a file named <filename>tablespace_map</> 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> |