Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit1b73681

Browse files
committed
Add:
>> * 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]
1 parent33cd270 commit1b73681

File tree

2 files changed

+21
-2
lines changed

2 files changed

+21
-2
lines changed

‎doc/TODO

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Thu Jan 510:13:26 EST 2006
5+
Last updated:Thu Jan 511:23:42 EST 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1014,6 +1014,16 @@ Write-Ahead Log
10141014
remove the 'fsync' parameter (which results in an an inconsistent
10151015
database) in favor of this capability.
10161016

1017+
* Allow control over which tables are WAL-logged
1018+
1019+
Allow tables to bypass WAL writes and just fsync() dirty pages on
1020+
commit. To do this, only a single writer can modify the table, and
1021+
writes must happen only on new pages. Readers can continue accessing
1022+
the table. Another option is to avoid transaction logging entirely
1023+
and truncate or drop the table on crash recovery. These should be
1024+
implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
1025+
TRUNCATE | STABLE | DEFAULT ]. [wallog]
1026+
10171027

10181028
Optimizer / Executor
10191029
====================

‎doc/src/FAQ/TODO.html

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated: Thu Jan 510:13:26 EST 2006
11+
Last updated: Thu Jan 511:23:42 EST 2006
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -918,6 +918,15 @@ <h1><a name="section_19">Write-Ahead Log</a></h1>
918918
committed transactions but still be consistent. We could perhaps
919919
remove the 'fsync' parameter (which results in an an inconsistent
920920
database) in favor of this capability.
921+
</p>
922+
</li><li>Allow control over which tables are WAL-logged
923+
<p> Allow tables to bypass WAL writes and just fsync() dirty pages on
924+
commit. To do this, only a single writer can modify the table, and
925+
writes must happen only on new pages. Readers can continue accessing
926+
the table. Another option is to avoid transaction logging entirely
927+
and truncate or drop the table on crash recovery. These should be
928+
implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
929+
TRUNCATE | STABLE | DEFAULT ]. [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?wallog">wallog</a>]
921930
</p>
922931
</li></ul>
923932
<h1><aname="section_20">Optimizer / Executor</a></h1>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp