database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-03 09:13:20 +03:00
Code Activity

Add:

Browse Source 
> * Consider sorting hash buckets so entries can be found using a binary
>   search, rather than a linear scan
> * In hash indexes, consider storing the hash value with or instead
>   of the key itself
This commit is contained in:
Bruce Momjian
2005-05-27 22:07:26 +00:00
parent 770156e157
commit 42319310dc
2 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TODO
View File

@@ -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 May 27 18:01:15 EDT 2005 Last updated: Fri May 27 18:07:21 EDT 2005
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.
@@ -351,6 +351,10 @@ Indexes
several hash buckets could be stored on a single page and greater several hash buckets could be stored on a single page and greater
granularity used for the hash algorithm. granularity used for the hash algorithm.
* Consider sorting hash buckets so entries can be found using a binary
search, rather than a linear scan
* In hash indexes, consider storing the hash value with or instead
of the key itself
* Allow accurate statistics to be collected on indexes with more than * Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics one column or expression indexes, perhaps using per-index statistics
* Add fillfactor to control reserved free space during index creation * Add fillfactor to control reserved free space during index creation

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

@@ -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 May 27 18:01:15 EDT 2005 Last updated: Fri May 27 18:07:21 EDT 2005
</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>.
@@ -324,6 +324,10 @@ first.
several hash buckets could be stored on a single page and greater several hash buckets could be stored on a single page and greater
granularity used for the hash algorithm. granularity used for the hash algorithm.
</p> </p>
</li><li>Consider sorting hash buckets so entries can be found using a binary
search, rather than a linear scan
</li><li>In hash indexes, consider storing the hash value with or instead
of the key itself
</li><li>Allow accurate statistics to be collected on indexes with more than </li><li>Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics one column or expression indexes, perhaps using per-index statistics
</li><li>Add fillfactor to control reserved free space during index creation </li><li>Add fillfactor to control reserved free space during index creation