database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

redo record -> undo record, Tom Lane.

Browse Source
This commit is contained in:
Bruce Momjian
2001-05-15 13:57:37 +00:00
parent 9478206d32
commit 3848a14ed7
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/wal.sgml
View File

@ -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"> <chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title> <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@ -243,7 +243,7 @@
log (known as the redo record) it should start the REDO operation, log (known as the redo record) it should start the REDO operation,
since any changes made to data files before that record are already since any changes made to data files before that record are already
on disk. After a checkpoint has been made, any log segments written 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 disk space in the <acronym>WAL</acronym> directory. (When
<acronym>WAL</acronym>-based <acronym>BAR</acronym> is implemented, <acronym>WAL</acronym>-based <acronym>BAR</acronym> is implemented,
the log segments can be archived instead of just being removed.) the log segments can be archived instead of just being removed.)