postgres.git / summary / log / commit / refs
commit e7893db5cfc85f9e996841f833b29348444150cd
Author: Bruce Momjian <bruce@momjian.us>
Date: Thu Jan 05 16:26:49 2006 +0000
First released in: 8.2.0
Update wording:
< the table. Another option is to avoid transaction logging entirely
< and truncate or drop the table on crash recovery. These should be
< implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
< TRUNCATE | STABLE | DEFAULT ]. [wallog]
> the table. This would affect COPY, and perhaps INSERT/UPDATE too.
> Another option is to avoid transaction logging entirely and truncate
> or drop the table on crash recovery. These should be implemented
> using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
> STABLE | DEFAULT ]. [wallog]
doc/TODO | 11 ++++++-----
doc/src/FAQ/TODO.html | 11 ++++++-----
2 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index dc7c97ffbc7..0c0bf9e61fd 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Thu Jan 5 11:23:42 EST 2006
+Last updated: Thu Jan 5 11:26:44 EST 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1019,10 +1019,11 @@ Write-Ahead Log
Allow tables to bypass WAL writes and just fsync() dirty pages on
commit. To do this, only a single writer can modify the table, and
writes must happen only on new pages. Readers can continue accessing
- the table. Another option is to avoid transaction logging entirely
- and truncate or drop the table on crash recovery. These should be
- implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
- TRUNCATE | STABLE | DEFAULT ]. [wallog]
+ the table. This would affect COPY, and perhaps INSERT/UPDATE too.
+ Another option is to avoid transaction logging entirely and truncate
+ or drop the table on crash recovery. These should be implemented
+ using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
+ STABLE | DEFAULT ]. [wallog]
Optimizer / Executor
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 0cbe43fb1d2..8b2f9541586 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Thu Jan 5 11:23:42 EST 2006
+Last updated: Thu Jan 5 11:26:44 EST 2006
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -923,10 +923,11 @@ first.
<p> Allow tables to bypass WAL writes and just fsync() dirty pages on
commit. To do this, only a single writer can modify the table, and
writes must happen only on new pages. Readers can continue accessing
- the table. Another option is to avoid transaction logging entirely
- and truncate or drop the table on crash recovery. These should be
- implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
- TRUNCATE | STABLE | DEFAULT ]. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
+ the table. This would affect COPY, and perhaps INSERT/UPDATE too.
+ Another option is to avoid transaction logging entirely and truncate
+ or drop the table on crash recovery. These should be implemented
+ using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
+ STABLE | DEFAULT ]. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
</p>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>
[parent: 1b736817d076]