Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitf8c2d49

Browse files
committed
doc: Clarify how to generate backup files with non-exclusive backups
The current instructions describing how to write the backup_label andtablespace_map files are confusing. For example, opening a file in textmode on Windows and copy-pasting the file's contents would result in afailure at recovery because of the extra CRLF characters generated. Thedocumentation was not stating that clearly, and per discussion this isnot considered as a supported scenario.This commit extends a bit the documentation to mention that it may berequired to open the file in binary mode before writing its data.Reported-by: Wang ShenhaoAuthor: David SteeleReviewed-by: Andrew Dunstan, Magnus HaganderDiscussion:https://postgr.es/m/8373f61426074f2cb6be92e02f838389@G08CNEXMBPEKD06.g08.fujitsu.localBackpatch-through: 9.6
1 parent75e66ee commitf8c2d49

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

‎doc/src/sgml/backup.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -904,7 +904,8 @@ SELECT * FROM pg_stop_backup(false, true);
904904
<filename>backup_label</filename> in the root directory of the backup. The
905905
third field should be written to a file named
906906
<filename>tablespace_map</filename> unless the field is empty. These files are
907-
vital to the backup working, and must be written without modification.
907+
vital to the backup working and must be written byte for byte without
908+
modification, which may require opening the file in binary mode.
908909
</para>
909910
</listitem>
910911
<listitem>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp