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:Sun Apr 6 22: 14:10 EDT 2008
11+ Last updated:Thu Apr10 14:57:53 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 > .
@@ -1063,6 +1063,10 @@ <h1><a name="section_12">Indexes</a></h1>
10631063</ p >
10641064< p > < a href ="http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php "> http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php</ a >
10651065< a href ="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php "> http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php</ a >
1066+ < a href ="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php "> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php</ a >
1067+ < a href ="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php "> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php</ a >
1068+ < a href ="http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php "> http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php</ a >
1069+ < a href ="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php "> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php</ a >
10661070</ p >
10671071</ li > < li > Allow accurate statistics to be collected on indexes with more than
10681072 one column or expression indexes, perhaps using per-index statistics
@@ -1083,6 +1087,8 @@ <h1><a name="section_12">Indexes</a></h1>
10831087< a href ="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php "> http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php</ a >
10841088< a href ="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php "> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php</ a >
10851089< a href ="http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php "> http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php</ a >
1090+ < a href ="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php "> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php</ a >
1091+ < a href ="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php "> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php</ a >
10861092</ p >
10871093</ li > < li > Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
10881094< p > This is difficult because you must upgrade to an exclusive table lock
@@ -1095,6 +1101,9 @@ <h1><a name="section_12">Indexes</a></h1>
10951101 single heap scan, and have pg_restore use it
10961102</ li > < li > Consider sorting entries before inserting into btree index
10971103< p > < a href ="http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php "> http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php</ a >
1104+ </ p >
1105+ </ li > < li > Allow index scans to return matching index keys
1106+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php "> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php</ a >
10981107</ p >
10991108</ li > < li > Inheritance
11001109< ul >
@@ -1192,6 +1201,9 @@ <h1><a name="section_14">Cache Usage</a></h1>
11921201 changes during the heap scan a counter could be set at the start and
11931202 checked at the end --- if it is the same, the table has not been
11941203 modified --- any table change would increment the counter.
1204+ </ p >
1205+ < p > < a href ="http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php "> http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php</ a >
1206+ < a href ="http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php "> http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php</ a >
11951207</ p >
11961208</ li > < li > Consider automatic caching of statements at various levels:
11971209< ul >