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

Commit7740991

Browse files
committed
Add:
> * Speed WAL recovery by allowing more than one page to be prefetched>> This involves having a separate process that can be told which pages> the recovery process will need in the near future.>http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php>
1 parent37cb2b7 commit7740991

File tree

2 files changed

+32
-15
lines changed

2 files changed

+32
-15
lines changed

‎doc/TODO

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
PostgreSQL TODO List
22
====================
33
Current maintainer:Bruce Momjian (bruce@momjian.us)
4-
Last updated:Mon Mar 310:06:41 EST 2008
4+
Last updated:Mon Mar 313:45:12 EST 2008
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -138,11 +138,13 @@ Administration
138138
o Allow a warm standby system to also allow read-only statements
139139
[pitr]
140140

141-
This is useful for checking PITR recovery.
142141
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
143142

144143
o %Create dump tool for write-ahead logs for use in determining
145144
transaction id for point-in-time recovery
145+
146+
This is useful for checking PITR recovery.
147+
146148
o Allow recovery.conf to support the same syntax as
147149
postgresql.conf, including quoting
148150

@@ -979,7 +981,8 @@ Indexes
979981

980982

981983
* Hash
982-
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
984+
985+
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
983986

984987
o Pack hash index buckets onto disk pages more efficiently
985988

@@ -1234,6 +1237,13 @@ Write-Ahead Log
12341237
tables probably cannot have indexes. One complexity is the handling
12351238
of indexes on TOAST tables.
12361239

1240+
* Speed WAL recovery by allowing more than one page to be prefetched
1241+
1242+
This involves having a separate process that can be told which pages
1243+
the recovery process will need in the near future.
1244+
http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php
1245+
1246+
12371247

12381248
Optimizer / Executor
12391249
====================

‎doc/src/FAQ/TODO.html

Lines changed: 19 additions & 12 deletions
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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Mon Mar 310:06:41 EST 2008
11+
Last updated: Mon Mar 313:45:12 EST 2008
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>.
@@ -128,11 +128,12 @@ <h1><a name="section_2">Administration</a></h1>
128128
<ul>
129129
<li>Allow a warm standby system to also allow read-only statements
130130
[<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
131-
<p> This is useful for checking PITR recovery.
132-
<ahref="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php</a>
131+
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php</a>
133132
</p>
134133
</li><li>%Create dump tool for write-ahead logs for use in determining
135134
transaction id for point-in-time recovery
135+
<p> This is useful for checking PITR recovery.
136+
</p>
136137
</li><li>Allow recovery.conf to support the same syntax as
137138
postgresql.conf, including quoting
138139
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php</a>
@@ -871,25 +872,26 @@ <h1><a name="section_10">Indexes</a></h1>
871872
digital trees (see Aoki)
872873
</li></ul>
873874
</li><li>Hash
874-
<ahref="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php</a>
875-
<ul>
876-
<li>Pack hash index buckets onto disk pages more efficiently
875+
</li></ul>
876+
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php</a>
877+
</p>
878+
<ul>
879+
<li>Pack hash index buckets onto disk pages more efficiently
877880
<p> Currently only one hash bucket can be stored on a page. Ideally
878881
several hash buckets could be stored on a single page and greater
879882
granularity used for the hash algorithm.
880883
</p>
881884
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a>
882885
</p>
883-
</li><li>Consider sorting hash buckets so entries can be found using a
886+
</li><li>Consider sorting hash buckets so entries can be found using a
884887
binary search, rather than a linear scan
885-
</li><li>In hash indexes, consider storing the hash value with or instead
888+
</li><li>In hash indexes, consider storing the hash value with or instead
886889
of the key itself
887-
</li><li>Add WAL logging for crash recovery
888-
</li><li>Allow multi-column hash indexes
889-
</li><li>During index creation, pre-sort the tuples to improve build speed
890+
</li><li>Add WAL logging for crash recovery
891+
</li><li>Allow multi-column hash indexes
892+
</li><li>During index creation, pre-sort the tuples to improve build speed
890893
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php</a>
891894
</p>
892-
</li></ul>
893895
</li></ul>
894896
<h1><aname="section_11">Fsync</a></h1>
895897

@@ -1096,6 +1098,11 @@ <h1><a name="section_16">Write-Ahead Log</a></h1>
10961098
crash recovery. Readers can continue accessing the table. Such
10971099
tables probably cannot have indexes. One complexity is the handling
10981100
of indexes on TOAST tables.
1101+
</p>
1102+
</li><li>Speed WAL recovery by allowing more than one page to be prefetched
1103+
<p> This involves having a separate process that can be told which pages
1104+
the recovery process will need in the near future.
1105+
<ahref="http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php</a>
10991106
</p>
11001107
</li></ul>
11011108
<h1><aname="section_17">Optimizer / Executor</a></h1>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp