From: Bruce Momjian Date: Sat, 4 Feb 2006 03:23:21 +0000 (+0000) Subject: Update walcontrol item: X-Git-Tag: REL9_0_0~8475 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=bc6a824ca6c1299be32a47652e7afd3704778021;p=pg-rex%2Fsyncrep.git Update walcontrol item: < * Allow control over which tables are WAL-logged > * Allow control over which tables are WAL-logged [walcontrol] 1038c1038,1039 < stable logging probably can not have indexes. [walcontrol] > stable logging probably can not have indexes. One complexity is > the handling of indexes on TOAST tables. --- diff --git a/doc/TODO b/doc/TODO index 62b5f2ff7d..d7e210651f 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: Wed Feb 1 12:32:41 EST 2006 +Last updated: Fri Feb 3 22:23:19 EST 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1024,7 +1024,7 @@ 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 control over which tables are WAL-logged [walcontrol] 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 @@ -1035,7 +1035,8 @@ Write-Ahead Log using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 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. [walcontrol] + stable logging probably can not have indexes. One complexity is + the handling of indexes on TOAST tables. Optimizer / Executor diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 67628148c8..9aafe3e9c3 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Wed Feb 1 12:32:41 EST 2006 +Last updated: Fri Feb 3 22:23:19 EST 2006

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -928,7 +928,7 @@ first. 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 control over which tables are WAL-logged [walcontrol]

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 @@ -938,7 +938,8 @@ first. using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 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. [walcontrol] + stable logging probably can not have indexes. One complexity is + the handling of indexes on TOAST tables.