PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Aug 26 15:10:29 EDT 2005
+Last updated: Fri Aug 26 15:32:39 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
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.
+ 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.
Exotic Features
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Fri Aug 26 15:10:29 EDT 2005
+Last updated: Fri Aug 26 15:32:39 EDT 2005
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
</li><li>Track dependencies in function bodies and recompile/invalidate
<p> 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.
+ 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.
</p>
</li></ul>
<h1><a name="section_12">Exotic Features</a></h1>