Adjust documentation about pg_pltemplate to reflect latest thinking.

It's more likely that pg_pltemplate will go away in the future than
that we'll add additional specialized infrastructure for it.

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index b14fb72cab899f605cdf358619f49144f08f4a38..cc0cbe134c4084115bb810626a51312435410261 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -4211,7 +4211,7 @@
      
       tmplacl
       aclitem[]
-      Access privileges for template (not yet used)
+      Access privileges for template (not actually used)
      
 
     
@@ -4222,16 +4222,17 @@
    There are not currently any commands that manipulate procedural language
    templates; to change the built-in information, a superuser must modify
    the table using ordinary INSERT, DELETE,
-   or UPDATE commands.  It is likely that a future
-   release of PostgreSQL will offer
-   commands to change the entries in a cleaner fashion.
+   or UPDATE commands.
   
 
-  
-   When implemented, the tmplacl field will provide
-   access control for the template itself (i.e., the right to create a
-   language using it), not for the languages created from the template.
-  
+  
+   
+    It is likely that pg_pltemplate will be removed in some
+    future release of PostgreSQL, in favor of
+    keeping this knowledge about procedural languages in their respective
+    extension installation scripts.
+   
+