|
8 | 8 | <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
9 | 9 | <h1><a name="section_1">PostgreSQL TODO List</a></h1>
|
10 | 10 | <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
11 |
| -Last updated: Sat Jan 13 10:13:24 EST 2007 |
| 11 | +Last updated: Tue Jan 16 22:43:34 EST 2007 |
12 | 12 | </p>
|
13 | 13 | <p>The most recent version of this document can be viewed at<br/>
|
14 | 14 | <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
|
@@ -315,7 +315,7 @@ <h1><a name="section_5">Functions</a></h1>
|
315 | 315 | </li><li>Add ISO day of week format 'ID' to to_char() where Monday = 1
|
316 | 316 | </li><li>Add a field 'isoyear' to extract(), based on the ISO week
|
317 | 317 | </li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
|
318 |
| - </li><li>Allow inlining of set-returning functions |
| 318 | + </li><li>Implement inlining of set-returning functions defined in SQL |
319 | 319 | </li><li>Allow SQL-language functions to return results from RETURNING queries
|
320 | 320 | </li></ul>
|
321 | 321 | <h1><a name="section_6">Multi-Language Support</a></h1>
|
@@ -835,6 +835,8 @@ <h1><a name="section_12">Indexes</a></h1>
|
835 | 835 | <p> Currently only one hash bucket can be stored on a page. Ideally
|
836 | 836 | several hash buckets could be stored on a single page and greater
|
837 | 837 | granularity used for the hash algorithm.
|
| 838 | +</p> |
| 839 | +<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a> |
838 | 840 | </p>
|
839 | 841 | </li><li>Consider sorting hash buckets so entries can be found using a
|
840 | 842 | binary search, rather than a linear scan
|
@@ -873,6 +875,12 @@ <h1><a name="section_14">Cache Usage</a></h1>
|
873 | 875 | get a count directly from a unique index, but for this to be
|
874 | 876 | faster than a sequential scan it must avoid access to the heap
|
875 | 877 | to obtain tuple visibility information.
|
| 878 | +</p> |
| 879 | + </li><li>Provide a way to calculate an "estimated COUNT(*)" |
| 880 | +<p> Perhaps by using the optimizer's cardinality estimates or random |
| 881 | + sampling. |
| 882 | +</p> |
| 883 | +<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a> |
876 | 884 | </p>
|
877 | 885 | </li><li>Allow data to be pulled directly from indexes
|
878 | 886 | <p> Currently indexes do not have enough tuple visibility information
|
@@ -958,15 +966,16 @@ <h1><a name="section_15">Vacuum</a></h1>
|
958 | 966 | </li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
|
959 | 967 | empty?
|
960 | 968 | </li><li>Consider logging activity either to the logs or a system view
|
961 |
| - </li><li>Turn on by default |
962 |
| -<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php</a> |
963 |
| -</p> |
| 969 | + </li><li>-<em>Turn on by default</em> |
964 | 970 | </li></ul>
|
965 | 971 | </li></ul>
|
966 | 972 | <h1><a name="section_16">Locking</a></h1>
|
967 | 973 |
|
968 | 974 | <ul>
|
969 | 975 | <li>Fix priority ordering of read and write light-weight locks (Neil)
|
| 976 | +<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php</a> |
| 977 | + <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php</a> |
| 978 | +</p> |
970 | 979 | </li></ul>
|
971 | 980 | <h1><a name="section_17">Startup Time Improvements</a></h1>
|
972 | 981 |
|
|
0 commit comments