postgres.git / summary / log / commit / refs
commit 1b736817d0761db12d370ab7a366eb3735eff571
Author: Bruce Momjian <bruce@momjian.us>
Date: Thu Jan 05 16:23:48 2006 +0000
First released in: 8.2.0
Add:
>
> * Allow control over which tables are WAL-logged
>
> 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]
doc/TODO | 12 +++++++++++-
doc/src/FAQ/TODO.html | 11 ++++++++++-
2 files changed, 21 insertions(+), 2 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index d8c5cc4129e..dc7c97ffbc7 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 10:13:26 EST 2006
+Last updated: Thu Jan 5 11:23:42 EST 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1014,6 +1014,16 @@ Write-Ahead Log
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
+* Allow control over which tables are WAL-logged
+
+ 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]
+
Optimizer / Executor
====================
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 7715d600470..0cbe43fb1d2 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 10:13:26 EST 2006
+Last updated: Thu Jan 5 11:23:42 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>.
@@ -918,6 +918,15 @@ first.
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
+</p>
+ </li><li>Allow control over which tables are WAL-logged
+<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>]
</p>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>
[parent: 33cd2706ad5a]