8000 Update TODO description for GIT: · postgrespro/postgres_cluster@9dd1049 · GitHub
[go: up one dir, main page]
Skip to content
8000

Commit 9dd1049

Browse files
bmomjianbmomjian
committed
Update TODO description for GIT:
* Consider smaller indexes that record a range of values per heap page, rather than having one index entry for every heap row
1 parent 380d1ee commit 9dd1049

File tree

2 files changed

+9
-7
lines changed
< 10000 div data-hpc="true">

2 files changed

+9
-7
lines changed

‎doc/TODO

Lines changed: 4 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: Wed Apr 23 22:24:23 EDT 2008
4+
Last updated: Thu Apr 24 11:53:48 EDT 2008
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1257,9 +1257,10 @@ Indexes
12571257
http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php
12581258
http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php
12591259

1260-
* Consider compressing indexes by storing key values duplicated in
1261-
several rows as a single index entry
1260+
* Consider smaller indexes that record a range of values per heap page,
1261+
rather than having one index entry for every heap row
12621262

1263+
This is useful if the heap is clustered by the indexed values.
12631264
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php
12641265
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
12651266
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php

‎doc/src/FAQ/TODO.html

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
99
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Wed Apr 23 22:24:23 EDT 2008
11+
Last updated: Thu Apr 24 11:53:48 EDT 2008
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -1090,9 +1090,10 @@ <h1><a name="section_12">Indexes</a></h1>
10901090
<a href="http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php">http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php</a>
10911091
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php</a>
10921092
</p>
1093-
</li><li>Consider compressing indexes by storing key values duplicated in
1094-
several rows as a single index entry
1095-
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php</a>
1093+
</li><li>Consider smaller indexes that record a range of values per heap page,
1094+
rather than having one index entry for every heap row
1095+
<p> This is useful if the heap is clustered by the indexed values.
1096+
<a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php</a>
10961097
<a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php</a>
10971098
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php</a>
10981099
<a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php</a>

0 commit comments

Comments
 (0)
0