Cache plan invalidation

The current TODO list has:
Dependency Checking===================* Flush cached query plans when the dependent objects change,  when the
cardinalityof parameters changes dramatically, or  when new ANALYZE statistics are available  A more complex solution
wouldbe to save multiple plans for different  cardinality and use the appropriate plan based on the EXECUTE values.*
Trackdependencies in function bodies and recompile/invalidate  This is particularly important for references to
temporarytables  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround  in PL/PgSQL is to use EXECUTE.
Onecomplexity is that a function  might itself drop and recreate dependent tables, causing it to  invalidate its own
queryplan.
 

Which of these are done or not done?

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +