PostgreSQL TODO List

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

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

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

Last updated:Mon Feb6 21:08:10 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 [walcontrol]

* Allow WAL logging to be turned off for a table, but the table

might be dropped or truncated during crash recovery [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

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 ]. Tables using non-default logging should not use

referential integrity with default-logging tables, and tables using

stable logging probably can not have indexes. One complexity is

the handling of indexes on TOAST tables.

commit. This should be implemented using ALTER TABLE, e.g. ALTER

TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using

non-default logging should not use referential integrity with

default-logging tables. A table without dirty buffers during a

crash could perhaps avoid the drop/truncate.

* Allow WAL logging to be turned off for a table, but the table would

avoid being truncated/dropped [walcontrol]

To do this, only a single writer can modify the table, and writes

must happen only on new pages so the new pages can be removed during

crash recovery. Readers can continue accessing the table. Such

tables probably cannot 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:Fri Feb3 22:23:19 EST 2006

Last updated:Mon Feb6 21:08:10 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>.

<li>%Remove behavior of postmaster -o

</li><li>-<em>%Allow pooled connections to list all prepared statements</em>

</li><li>-*%Allow pooled connections to list all prepared statements*

<p> This would allow an application inheriting a pooled connection to know

the statements prepared in the current session.

</li><li>%Allow postgresql.conf file values to be changed via an SQL

API, perhaps using SET GLOBAL

</li><li>Allow the server to be stopped/restarted via an SQL API

</li><li>-<em>Issue a warning if a change-on-restart-only postgresql.conf value

is modified and the server config files are reloaded</em>

</li><li>-<em>Issue a warning if a change-on-restart-only postgresql.conf value</em>

is modified and the server config files are reloaded

</li><li>Mark change-on-restart-only values in postgresql.conf

</li><li>Tablespaces

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

</li><li>Allow WAL logging to be turned off for a table, but the table

might be dropped or truncated during crash recovery [<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

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 ]. Tables using non-default logging should not use

referential integrity with default-logging tables, and tables using

stable logging probably can not have indexes. One complexity is

the handling of indexes on TOAST tables.

commit. This should be implemented using ALTER TABLE, e.g. ALTER

TABLE PERSISTENCE [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo? DROP | TRUNCATE | DEFAULT"> DROP | TRUNCATE | DEFAULT</a>]. Tables using

non-default logging should not use referential integrity with

default-logging tables. A table without dirty buffers during a

crash could perhaps avoid the drop/truncate.

</li><li>Allow WAL logging to be turned off for a table, but the table would

avoid being truncated/dropped [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]

<p> To do this, only a single writer can modify the table, and writes

must happen only on new pages so the new pages can be removed during

crash recovery. Readers can continue accessing the table. Such

tables probably cannot have indexes. One complexity is the handling

of indexes on TOAST tables.

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