mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Split up wal-logging items:

Browse Source 
< * 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]
<   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.
This commit is contained in:
Bruce Momjian 2006-02-07 02:08:08 +00:00
parent 8bf47f455f
commit 04a942e31e
2 changed files with 36 additions and 27 deletions
doc
TODO
src/FAQ
TODO.html

29
doc/TODO

@ -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: Fri Feb 3 22:23:19 EST 2006 Last updated: Mon Feb 6 21:08:10 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,19 +1024,24 @@ 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 [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 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. This should be implemented using ALTER TABLE, e.g. ALTER
writes must happen only on new pages. Readers can continue accessing TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using
the table. This would affect COPY, and perhaps INSERT/UPDATE too. non-default logging should not use referential integrity with
Another option is to avoid transaction logging entirely and truncate default-logging tables. A table without dirty buffers during a
or drop the table on crash recovery. These should be implemented crash could perhaps avoid the drop/truncate.
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
STABLE | DEFAULT ]. Tables using non-default logging should not use * Allow WAL logging to be turned off for a table, but the table would
referential integrity with default-logging tables, and tables using avoid being truncated/dropped [walcontrol]
stable logging probably can not have indexes. One complexity is
the handling of indexes on TOAST tables. 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 Optimizer / Executor

34
doc/src/FAQ/TODO.html

@ -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: Fri Feb 3 22:23:19 EST 2006 Last updated: Mon Feb 6 21:08:10 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>.
@ -26,7 +26,7 @@ first.
<ul> <ul>
<li>%Remove behavior of postmaster -o <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 <p> This would allow an application inheriting a pooled connection to know
the statements prepared in the current session. the statements prepared in the current session.
</p> </p>
@ -79,8 +79,8 @@ first.
</li><li>%Allow postgresql.conf file values to be changed via an SQL </li><li>%Allow postgresql.conf file values to be changed via an SQL
API, perhaps using SET GLOBAL API, perhaps using SET GLOBAL
</li><li>Allow the server to be stopped/restarted via an SQL API </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 </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</em> is modified and the server config files are reloaded
</li><li>Mark change-on-restart-only values in postgresql.conf </li><li>Mark change-on-restart-only values in postgresql.conf
</li></ul> </li></ul>
</li><li>Tablespaces </li><li>Tablespaces
@ -928,18 +928,22 @@ 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 [<a href="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 [<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. This should be implemented using ALTER TABLE, e.g. ALTER
writes must happen only on new pages. Readers can continue accessing TABLE PERSISTENCE [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo? DROP | TRUNCATE | DEFAULT "> DROP | TRUNCATE | DEFAULT </a>]. Tables using
the table. This would affect COPY, and perhaps INSERT/UPDATE too. non-default logging should not use referential integrity with
Another option is to avoid transaction logging entirely and truncate default-logging tables. A table without dirty buffers during a
or drop the table on crash recovery. These should be implemented crash could perhaps avoid the drop/truncate.
using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | </p>
STABLE | DEFAULT ]. Tables using non-default logging should not use </li><li>Allow WAL logging to be turned off for a table, but the table would
referential integrity with default-logging tables, and tables using avoid being truncated/dropped [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
stable logging probably can not have indexes. One complexity is <p> To do this, only a single writer can modify the table, and writes
the handling of indexes on TOAST tables. 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.
</p> </p>
</li></ul> </li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1> <h1><a name="section_20">Optimizer / Executor</a></h1>