Re-add FAQ item:

    4.19) Why do I get "relation with OID #####
    does not exist" errors when accessing temporary tables in PL/PgSQL
    functions?

diff --git a/doc/FAQ b/doc/FAQ
index ef35027ab087df5feee68504dfbcd44fc5f92a24..f41d21e20d5e1e06f61739fffc2ba058429784f7 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Fri Oct 12 23:36:59 EDT 2007
+   Last updated: Wed Oct 17 13:34:42 EDT 2007
    
    Current maintainer: Bruce Momjian ([email protected])
    
@@ -78,8 +78,10 @@
    4.16) How do I perform an outer join?
    4.17) How do I perform queries using multiple databases?
    4.18) How do I return multiple rows or columns from a function?
-   4.19) What replication solutions are available?
-   4.20) Why are my table and column names not recognized in my query?
+   4.19) Why do I get "relation with OID ##### does not exist" errors
+   when accessing temporary tables in PL/PgSQL functions?
+   4.20) What replication solutions are available?
+   4.21) Why are my table and column names not recognized in my query?
    Why is capitalization not preserved?
      _________________________________________________________________
    
@@ -790,7 +792,20 @@
    It is easy using set-returning functions,
    http://www.postgresql.org/docs/techdocs.17.
    
-  4.19) What replication solutions are available?
+  4.19) Why do I get "relation with OID ##### does not exist" errors when
+  accessing temporary tables in PL/PgSQL functions?
+  
+   In PostgreSQL versions < 8.3, PL/PgSQL caches function scripts, and an
+   unfortunate side effect is that if a PL/PgSQL function accesses a
+   temporary table, and that table is later dropped and recreated, and
+   the function called again, the function will fail because the cached
+   function contents still point to the old temporary table. The solution
+   is to use EXECUTE for temporary table access in PL/PgSQL. This will
+   cause the query to be reparsed every time.
+   
+   This problem does not occur in PostgreSQL 8.3 and later.
+   
+  4.20) What replication solutions are available?
   
    Though "replication" is a single term, there are several technologies
    for doing replication, with advantages and disadvantages for each.
@@ -809,7 +824,7 @@
    There are also commercial and hardware-based replication solutions
    available supporting a variety of replication models.
    
-  4.20) Why are my table and column names not recognized in my query? Why is
+  4.21) Why are my table and column names not recognized in my query? Why is
   capitalization not preserved?
   
    The most common cause of unrecognized names is the use of

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 38baf49798bf14975ad76f691b67a46097983899..78efa16078fae6bdfd1c5d91f3e740ab068bcecd 100644 (file)
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
   alink="#0000ff">
     Frequently Asked Questions (FAQ) for PostgreSQL
 
-    Last updated: Fri Oct 12 23:36:59 EDT 2007
+    Last updated: Wed Oct 17 13:34:42 EDT 2007
 
     Current maintainer: Bruce Momjian (
     "mailto:[email protected]">[email protected])
@@ -114,8 +114,11 @@
     databases?
      4.18) How do I return multiple rows or columns
     from a function?
-     4.19) What replication solutions are available?
-     4.20) Why are my table and column names not
+     4.19) Why do I get "relation with OID #####
+    does not exist" errors when accessing temporary tables in PL/PgSQL
+    functions?
+     4.20) What replication solutions are available?
+     4.21) Why are my table and column names not
     recognized in my query?  Why is capitalization not preserved?
 
 
@@ -1041,7 +1044,21 @@ length
     
     http://www.postgresql.org/docs/techdocs.17.
 
-    4.19) What replication solutions are available?
+    4.19) Why do I get "relation with OID #####
+    does not exist" errors when accessing temporary tables in PL/PgSQL
+    functions?
+
+    In PostgreSQL versions < 8.3, PL/PgSQL caches function scripts, and
+    an unfortunate side effect is that if a PL/PgSQL function accesses a
+    temporary table, and that table is later dropped and recreated, and
+    the function called again, the function will fail because the cached
+    function contents still point to the old temporary table. The solution
+    is to use EXECUTE for temporary table access in
+    PL/PgSQL. This will cause the query to be reparsed every time.
+
+    This problem does not occur in PostgreSQL 8.3 and later.
+
+    4.20) What replication solutions are available?
     
 
     Though "replication" is a single term, there are several technologies
@@ -1063,7 +1080,7 @@ length
     There are also commercial and hardware-based replication solutions
     available supporting a variety of replication models.
 
-    0">4.20) Why are my table and column names not
+    1">4.21) Why are my table and column names not
     recognized in my query?  Why is capitalization not preserved?
 
     The most common cause of unrecognized names is the use of
@@ -1080,5 +1097,6 @@ length
     Use only lowercase characters in identifiers
     Double-quote identifiers when referencing them in queries
     
+