aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2006-01-05 16:35:19 +0000
committerBruce Momjian <bruce@momjian.us>2006-01-05 16:35:19 +0000
commitac9e14d064a87c5ef441f7c2ed567c61b7420a43 (patch)
tree82d2bf0e295e7d6e45c70664b98314e83a057f89
parente7893db5cfc85f9e996841f833b29348444150cd (diff)
downloadpostgresql-ac9e14d064a87c5ef441f7c2ed567c61b7420a43.tar.gz
postgresql-ac9e14d064a87c5ef441f7c2ed567c61b7420a43.zip
Update wording:
< STABLE | DEFAULT ]. [wallog] > STABLE | DEFAULT ]. Tables using non-default logging should not use > referential integrity with default-logging tables, and tables using > stable logging probably can not have indexes. [wallog]
-rw-r--r--doc/TODO6
-rw-r--r--doc/src/FAQ/TODO.html6
2 files changed, 8 insertions, 4 deletions
diff --git a/doc/TODO b/doc/TODO
index 0c0bf9e61fd..488ad5fb568 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:26:44 EST 2006
+Last updated: Thu Jan 5 11:35:12 EST 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1023,7 +1023,9 @@ Write-Ahead Log
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]
+ STABLE | DEFAULT ]. Tables using non-default logging should not use
+ referential integrity with default-logging tables, and tables using
+ stable logging probably can not have indexes. [wallog]
Optimizer / Executor
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 8b2f9541586..93259ffe015 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:26:44 EST 2006
+Last updated: Thu Jan 5 11:35:12 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>.
@@ -927,7 +927,9 @@ first.
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>]
+ STABLE | DEFAULT ]. Tables using non-default logging should not use
+ referential integrity with default-logging tables, and tables using
+ stable logging probably can not have indexes. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
</p>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>