Skip to content

P
Postgres FD Implementation
Commit bc6a824c authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

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.
parent 3f898403
Hide whitespace changes
Inline Side-by-side
Showing with 8 additions and 6 deletions
doc/TODO
View file @ bc6a824c
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -1024,7 +1024,7 @@ Write-Ahead Log ...@@ -1024,7 +1024,7 @@ Write-Ahead Log
remove the 'fsync' parameter (which results in an an inconsistent remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability. 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 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 commit. To do this, only a single writer can modify the table, and
...@@ -1035,7 +1035,8 @@ Write-Ahead Log ...@@ -1035,7 +1035,8 @@ Write-Ahead Log
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
STABLE | DEFAULT ]. Tables using non-default logging should not use STABLE | DEFAULT ]. Tables using non-default logging should not use
referential integrity with default-logging tables, and tables using 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 Optimizer / Executor
......
doc/src/FAQ/TODO.html
View file @ bc6a824c
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Wed Feb 1 12:32:41 EST 2006 Last updated: Fri Feb 3 22:23:19 EST 2006
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -928,7 +928,7 @@ first. ...@@ -928,7 +928,7 @@ first.
remove the 'fsync' parameter (which results in an an inconsistent remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability. database) in favor of this capability.
</p> </p>
</li><li>Allow control over which tables are WAL-logged </li><li>Allow control over which tables are WAL-logged [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
<p> Allow tables to bypass WAL writes and just fsync() dirty pages on <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 commit. To do this, only a single writer can modify the table, and
writes must happen only on new pages. Readers can continue accessing writes must happen only on new pages. Readers can continue accessing
...@@ -938,7 +938,8 @@ first. ...@@ -938,7 +938,8 @@ first.
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
STABLE | DEFAULT ]. Tables using non-default logging should not use STABLE | DEFAULT ]. Tables using non-default logging should not use
referential integrity with default-logging tables, and tables using 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?walcontrol">walcontrol</a>] stable logging probably can not have indexes. One complexity is
the handling of indexes on TOAST tables.
</p> </p>
</li></ul> </li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1> <h1><a name="section_20">Optimizer / Executor</a></h1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment