@ -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 >