From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 17 Mar 2005 05:10:11 +0000 (+0000)
Subject: Mention tablespaces as a problem for using file system snapshots.
X-Git-Tag: REL8_1_0BETA1~1187
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=118bf5bc226ed023263486fcd5639918185003ed;p=postgresql

Mention tablespaces as a problem for using file system snapshots.
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 00efde7ee2..01d023aae0 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.57 2005/03/17 05:03:37 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.58 2005/03/17 05:10:11 momjian Exp $
 -->
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -365,7 +365,7 @@ tar -cf backup.tar /usr/local/pgsql/data
 
   <para>
    If your database is spread across multiple volumes (for example,
-   data files and WAL log on different disks) there may not be any way
+   if you are using tablespaces) there may not be any way
    to obtain exactly-simultaneous frozen snapshots of all the volumes.
    Read your file system documentation very carefully before trusting
    to the consistent-snapshot technique in such situations.  The safest