From f260edb144c1e3f33d5ecc3d00d5359ab675d238 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Thu, 10 Apr 2008 18:58:15 +0000
Subject: [PATCH] Add TODO URLs moved from open items queue:
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php
> * Allow index scans to return matching index keys
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
>
> http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php
> http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php
---
doc/TODO | 14 +++++++++++++-
doc/src/FAQ/TODO.html | 14 +++++++++++++-
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index 53bc85afb5b..7af6aa9eb77 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sun Apr 6 22:14:10 EDT 2008
+Last updated: Thu Apr 10 14:57:53 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1230,6 +1230,10 @@ Indexes
http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php
+ http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php
+ http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php
* Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
@@ -1253,6 +1257,8 @@ Indexes
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php
* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
@@ -1269,6 +1275,9 @@ Indexes
http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php
+* Allow index scans to return matching index keys
+
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
* Inheritance
@@ -1380,6 +1389,9 @@ Cache Usage
checked at the end --- if it is the same, the table has not been
modified --- any table change would increment the counter.
+ http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php
+ http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php
+
* Consider automatic caching of statements at various levels:
o Parsed query tree
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 7b81e7f9f3c..aa593d0dab9 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sun Apr 6 22:14:10 EDT 2008
+Last updated: Thu Apr 10 14:57:53 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1063,6 +1063,10 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php
+ http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php
+ http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php
Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
@@ -1083,6 +1087,8 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php
Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
This is difficult because you must upgrade to an exclusive table lock
@@ -1095,6 +1101,9 @@ first. There is also a developer's wiki at
single heap scan, and have pg_restore use it
Consider sorting entries before inserting into btree index
http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php
+
+ Allow index scans to return matching index keys
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
Inheritance
Consider automatic caching of statements at various levels: