rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-30 18:21:19 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add:

Browse Source 
>
> * Allow control over which tables are WAL-logged
>
>   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]
This commit is contained in:
Bruce Momjian 2006-01-05 16:23:48 +00:00
parent 33cd2706ad
commit 1b736817d0
2 changed files with 21 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Thu Jan 5 10:13:26 EST 2006
Last updated: Thu Jan 5 11:23:42 EST 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -1014,6 +1014,16 @@ Write-Ahead Log
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 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]
Optimizer / Executor
====================

11
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<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/>
Last updated: Thu Jan 5 10:13:26 EST 2006
Last updated: Thu Jan 5 11:23:42 EST 2006
</p>
<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>.
@ -918,6 +918,15 @@ first.
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
</p>
</li><li>Allow control over which tables are WAL-logged
<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 ]. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
</p>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>