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

Commit118bf5b

Browse files
committed
Mention tablespaces as a problem for using file system snapshots.
1 parentca2d085 commit118bf5b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/backup.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.57 2005/03/17 05:03:37 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.58 2005/03/17 05:10:11 momjian Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -365,7 +365,7 @@ tar -cf backup.tar /usr/local/pgsql/data
365365

366366
<para>
367367
If your database is spread across multiple volumes (for example,
368-
data files and WAL log on different disks) there may not be any way
368+
if you are using tablespaces) there may not be any way
369369
to obtain exactly-simultaneous frozen snapshots of all the volumes.
370370
Read your file system documentation very carefully before trusting
371371
to the consistent-snapshot technique in such situations. The safest

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp