From 43e9bab94a8d1d338f19ecadb12f66359b6b5532 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 3 Mar 2006 22:02:08 +0000
Subject: [PATCH] Rename Online Backup to Continuous Archiving.
---
doc/src/sgml/backup.sgml | 21 +++++++++++----------
doc/src/sgml/config.sgml | 4 ++--
doc/src/sgml/func.sgml | 4 ++--
doc/src/sgml/wal.sgml | 4 ++--
4 files changed, 17 insertions(+), 16 deletions(-)
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 9245c6278b6..6ee26bb9d2b 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.77 2006/02/24 14:03:01 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.78 2006/03/03 22:02:07 momjian Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -19,7 +19,7 @@ $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.77 2006/02/24 14:03:01 momjian E
<itemizedlist>
<listitem><para><acronym>SQL</> dump</para></listitem>
<listitem><para>File system level backup</para></listitem>
- <listitem><para>On-line backup</para></listitem>
+ <listitem><para>Continuous Archiving</para></listitem>
</itemizedlist>
Each has its own strengths and weaknesses.
</para>
@@ -372,11 +372,11 @@ tar -cf backup.tar /usr/local/pgsql/data
</para>
</sect1>
- <sect1 id="backup-online">
- <title>On-line backup and point-in-time recovery (PITR)</title>
+ <sect1 id="continuous-archiving">
+ <title>Continuous Archiving and Point-In-Time Recovery (PITR)</title>
<indexterm zone="backup">
- <primary>on-line backup</primary>
+ <primary>continuous archiving</primary>
</indexterm>
<indexterm zone="backup">
@@ -452,7 +452,8 @@ tar -cf backup.tar /usr/local/pgsql/data
</para>
<para>
- To recover successfully using an on-line backup, you need a continuous
+ To recover successfully using continuous archiving (also called "online
+ backup" by many database vendors), you need a continuous
sequence of archived WAL files that extends back at least as far as the
start time of your backup. So to get started, you should set up and test
your procedure for archiving WAL files <emphasis>before</> you take your
@@ -783,12 +784,12 @@ SELECT pg_stop_backup();
<function>pg_start_backup</> or <function>pg_stop_backup</>, and
you will therefore be left to your own devices to keep track of which
backup dump is which and how far back the associated WAL files go.
- It is generally better to follow the on-line backup procedure above.
+ It is generally better to follow the continuous archiving procedure above.
</para>
</sect2>
<sect2 id="backup-pitr-recovery">
- <title>Recovering with an On-line Backup</title>
+ <title>Recovering using a Continuous Archive Backup</title>
<para>
Okay, the worst has happened and you need to recover from your backup.
@@ -1120,11 +1121,11 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows
</para>
</sect2>
- <sect2 id="backup-online-caveats">
+ <sect2 id="continuous-archiving-caveats">
<title>Caveats</title>
<para>
- At this writing, there are several limitations of the on-line backup
+ At this writing, there are several limitations of the continuous archiving
technique. These will probably be fixed in future releases:
<itemizedlist>
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index dd64ffe3db2..710f1b93d16 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.47 2006/02/05 18:19:14 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.48 2006/03/03 22:02:07 momjian Exp $
-->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@@ -1387,7 +1387,7 @@ SET ENABLE_SEQSCAN TO OFF;
<para>
Turning off this parameter does not affect use of
WAL archiving for point-in-time recovery (PITR)
- (see <xref linkend="backup-online">).
+ (see <xref linkend="continuous-archiving">).
</para>
<para>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 8f0975af703..7d18f976021 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.307 2006/02/18 16:15:21 petere Exp $
+$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.308 2006/03/03 22:02:07 momjian Exp $
PostgreSQL documentation
-->
@@ -9808,7 +9808,7 @@ SELECT set_config('log_statement_stats', 'off', false);
<para>
For details about proper usage of these functions, see
- <xref linkend="backup-online">.
+ <xref linkend="continuous-archiving">.
</para>
<para>
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 576b63e0d2f..601a316cdc9 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.38 2005/11/04 23:14:02 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.39 2006/03/03 22:02:08 momjian Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
@@ -136,7 +136,7 @@
<para>
<acronym>WAL</acronym> also makes it possible to support on-line
backup and point-in-time recovery, as described in <xref
- linkend="backup-online">. By archiving the WAL data we can support
+ linkend="continuous-archiving">. By archiving the WAL data we can support
reverting to any time instant covered by the available WAL data:
we simply install a prior physical backup of the database, and
replay the WAL log just as far as the desired time. What's more,
--
GitLab