From cad7f831e1e62e3e39b4e881b9f2f668d762c349 Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Fri, 26 Aug 2005 19:32:43 +0000 Subject: [PATCH] Update based on user comments: < 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. --- doc/TODO | 6 ++++-- doc/src/FAQ/TODO.html | 6 ++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/TODO b/doc/TODO index 5f8cd01b1c0..e60941194c6 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: 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. @@ -621,7 +621,9 @@ Dependency Checking 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 4b84782b737..4a3a825286b 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@ <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>. @@ -563,7 +563,9 @@ first. </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> -- GitLab