PostgreSQL TODO List

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

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

Last updated:Thu Jan 5 11:23:42 EST 2006

Last updated:Thu Jan 5 11:26:44 EST 2006

The most recent version of this document can be viewed at

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

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

the table. 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]

the table. This would affect COPY, and perhaps INSERT/UPDATE too.

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]

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: Thu Jan 5 11:23:42 EST 2006

Last updated: Thu Jan 5 11:26:44 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>.

<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

the table. 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 ]. [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]

the table. This would affect COPY, and perhaps INSERT/UPDATE too.

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 ]. [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]

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