PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)

Last updated:Wed Feb1 12:32:41 EST 2006

Last updated:Fri Feb3 22:23:19 EST 2006

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

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

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

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>

Last updated:Wed Feb1 12:32:41 EST 2006

Last updated:Fri Feb3 22:23:19 EST 2006

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

remove the 'fsync' parameter (which results in an an inconsistent

database) in favor of this capability.

</li><li>Allow control over which tables are WAL-logged

</li><li>Allow control over which tables are WAL-logged [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]

<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

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. [<ahref="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.

<h1><aname="section_20">Optimizer / Executor</a></h1>