diff --git a/doc/TODO b/doc/TODO index 92f41e72265..d492324b3ea 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,8 +1,8 @@ - +z PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat May 5 10:47:39 EDT 2007 +Last updated: Sat May 5 11:39:57 EDT 2007 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -958,22 +958,10 @@ Triggers Dependency Checking =================== -* Flush cached query plans when the dependent objects change, - when the cardinality of parameters changes dramatically, or +* -Flush cached query plans when the dependent objects change or when new ANALYZE statistics are available - - A more complex solution would be to save multiple plans for different - cardinality and use the appropriate plan based on the EXECUTE values. - -* Track dependencies in function bodies and recompile/invalidate - - This is particularly important for references to temporary tables - in PL/PgSQL because PL/PgSQL caches query plans. The only workaround - in PL/PgSQL is to use EXECUTE. One complexity is that a function - might itself drop and recreate dependent tables, causing it to - invalidate its own query plan. - -* Invalidate prepared queries, like INSERT, when the table definition +* -Track dependencies in function bodies and recompile/invalidate +* -Invalidate prepared queries, like INSERT, when the table definition is altered diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index e4e59822490..2ed075d4ae2 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -2,14 +2,16 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sat May 5 10:47:39 EDT 2007
-
z
+PostgreSQL TODO List
+
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php
http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php
A more complex solution would be to save multiple plans for different - cardinality and use the appropriate plan based on the EXECUTE values. -
-This is particularly important for references to temporary tables - in PL/PgSQL because PL/PgSQL caches query plans. The only workaround - in PL/PgSQL is to use EXECUTE. One complexity is that a function - might itself drop and recreate dependent tables, causing it to - invalidate its own query plan. -
-http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php