Skip to content
Snippets Groups Projects
Commit d66f172f authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Don't document that UNDO is certain to be added in the future.

parent f170e61d
Branches
Tags
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 2 additions and 3 deletions
doc/src/sgml/wal.sgml
+ 2
− 3
View file @ d66f172f
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.15 2002/02/11 23:25:14 momjian Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.16 2002/07/05 19:06:11 momjian Exp $ -->
<chapter id="wal"> <chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title> <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
...@@ -80,8 +80,7 @@ ...@@ -80,8 +80,7 @@
<title>Future Benefits</title> <title>Future Benefits</title>
<para> <para>
In this first release of <acronym>WAL</acronym>, UNDO operation is UNDO operation is not implemented. This means that changes
not implemented, because of lack of time. This means that changes
made by aborted transactions will still occupy disk space and that made by aborted transactions will still occupy disk space and that
we still need a permanent <filename>pg_clog</filename> file to hold we still need a permanent <filename>pg_clog</filename> file to hold
the status of transactions, since we are not able to re-use the status of transactions, since we are not able to re-use
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment