From 2f1a78e200259c5ac4cb3b05fce0157e15a09464 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 22 Dec 2005 23:05:32 +0000 Subject: [PATCH] Update item: > > A more complex solution would be to save multiple plans for different > cardinality and use the appropriate plan based on the EXECUTE values. > --- doc/TODO | 6 +++++- doc/src/FAQ/TODO.html | 5 ++++- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/doc/TODO b/doc/TODO index 24f8e250f0..8251a96f48 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Sat Dec 17 14:03:20 EST 2005 +Last updated: Thu Dec 22 18:05:31 EST 2005 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -718,6 +718,10 @@ Dependency Checking * Flush cached query plans when the dependent objects change, when the cardinality of parameters changes dramatically, 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 32add687d5..8c358ea801 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Sat Dec 17 14:03:20 EST 2005 +Last updated: Thu Dec 22 18:05:31 EST 2005

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -655,6 +655,9 @@ first.

  • Flush cached query plans when the dependent objects change, when the cardinality of parameters changes dramatically, 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