Index: doc/src/sgml/maintenance.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v
retrieving revision 1.102
diff -c -c -r1.102 maintenance.sgml
*** doc/src/sgml/maintenance.sgml	3 Apr 2010 07:22:55 -0000	1.102
--- doc/src/sgml/maintenance.sgml	16 Apr 2010 02:21:23 -0000
***************
*** 643,648 ****
--- 643,654 ----
     </para>
  
     <para>
+     Temporary tables cannot be accessed by autovacuum.  Therefore,
+     appropriate vacuum and analyze operations should be performed via
+     session SQL commands.
+    </para>
+ 
+    <para>
      The default thresholds and scale factors are taken from
      <filename>postgresql.conf</filename>, but it is possible to override them
      on a table-by-table basis; see
Index: doc/src/sgml/ref/create_table.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v
retrieving revision 1.125
diff -c -c -r1.125 create_table.sgml
*** doc/src/sgml/ref/create_table.sgml	3 Apr 2010 07:23:00 -0000	1.125
--- doc/src/sgml/ref/create_table.sgml	16 Apr 2010 02:21:27 -0000
***************
*** 145,150 ****
--- 145,159 ----
       </para>
  
       <para>
+       The <link linkend="autovacuum">autovacuum daemon</link> cannot
+       access and therefore cannot vacuum or analyze temporary tables.
+       For this reason, appropriate vacuum and analyze operations should be
+       performed via session SQL commands.  For example, if a temporary
+       table is going to be used in complex queries, it is wise to run
+       <command>ANALYZE</> on the temporary table after it is populated.
+      </para>
+       
+      <para>
        Optionally, <literal>GLOBAL</literal> or <literal>LOCAL</literal>
        can be written before <literal>TEMPORARY</> or <literal>TEMP</>.
        This makes no difference in <productname>PostgreSQL</>, but see