open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source
REL7_3_STABLE
Bruce Momjian 24 years ago
parent f170e61d9b
commit d66f172f4b
1 changed files with 2 additions and 3 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 5
      doc/src/sgml/wal.sgml

5
doc/src/sgml/wal.sgml
Unescape View File

@ -1,4 +1,4 @@
<!-- $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 @@
<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

Write Preview
Loading…
Cancel
Save