diff options
author | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:15 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:15 +0900 |
commit | eb5e380a08a2d5ce13cb64d405d2966ffb8944b7 (patch) | |
tree | 9c764b862d74ea2872bfed93f4627330fcd8f517 /src/include/executor/nodeModifyTable.h | |
parent | 061003b27fde996b612d58cbdef6b1e0717e3063 (diff) | |
download | postgresql-eb5e380a08a2d5ce13cb64d405d2966ffb8944b7.tar.gz postgresql-eb5e380a08a2d5ce13cb64d405d2966ffb8944b7.zip |
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
Diffstat (limited to 'src/include/executor/nodeModifyTable.h')
0 files changed, 0 insertions, 0 deletions