diff options
author | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:00 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2021-04-02 16:37:00 +0900 |
commit | 6fb66c268df2de1112cac3cf0a6cf0a8b96ceaf0 (patch) | |
tree | 5cfc1a6ac8ccae281f87d4589b1b3524e69e24da /src/backend/tcop/postgres.c | |
parent | 98e5bd103f887326e381c509c2fbe879ba3ea2f3 (diff) | |
download | postgresql-6fb66c268df2de1112cac3cf0a6cf0a8b96ceaf0.tar.gz postgresql-6fb66c268df2de1112cac3cf0a6cf0a8b96ceaf0.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/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions