From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 15 May 2001 13:57:37 +0000 (+0000)
Subject: redo record -> undo record, Tom Lane.
X-Git-Tag: REL7_2_BETA1~1277
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3848a14ed7014bd6df0dfe8dedbeb545eb331e82;p=postgresql

redo record -> undo record, Tom Lane.
---

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 69616409e8..dfb90e6e6c 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.5 2001/03/16 05:44:33 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.6 2001/05/15 13:57:37 momjian Exp $ -->
 
 <chapter id="wal">
  <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@@ -243,7 +243,7 @@
    log (known as the redo record) it should start the REDO operation,
    since any changes made to data files before that record are already
    on disk. After a checkpoint has been made, any log segments written
-   before the redo record are removed, so checkpoints are used to free
+   before the undo records are removed, so checkpoints are used to free
    disk space in the <acronym>WAL</acronym> directory. (When
    <acronym>WAL</acronym>-based <acronym>BAR</acronym> is implemented,
    the log segments can be archived instead of just being removed.)