* Make pg_get_triggerdef documentation consistent with other pg_get_

functions
* Document pg_conversion_is_visible() which was created in one of my
previous patches and didn't get documented for some reason

Christopher Kings-Lynne

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index c8f242ca0003a80916869b8b8e86524a32042a40..093cc19afbfadc502bc7c4573ce063af1f279d5c 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
 
 
@@ -6757,6 +6757,12 @@ SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
        boolean
        is operator class visible in search path
       
+      
+       pg_conversion_is_visible(conversion_oid)
+       
+       boolean
+       is conversion visible in search path
+      
      
     
    
@@ -6776,16 +6782,20 @@ SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
    
     pg_opclass_is_visible
    
+   
+    pg_conversion_is_visible
+   
 
    
    pg_table_is_visible performs the check for
    tables (or views, or any other kind of pg_class entry).
    pg_type_is_visible,
    pg_function_is_visible,
-   pg_operator_is_visible, and
-   pg_opclass_is_visible perform the same sort of
-   visibility check for types, functions, operators, and operator
-   classes, respectively.  For functions and operators, an object in
+   pg_operator_is_visible,
+   pg_opclass_is_visible, and
+   pg_conversion_is_visible perform the same sort of
+   visibility check for types, functions, operators, operator classes
+   and conversions, respectively.  For functions and operators, an object in
    the search path is visible if there is no object of the same name
    and argument data type(s) earlier in the path.  For
    operator classes, both name and associated index access method are
@@ -6833,8 +6843,8 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
    extract information from the system catalogs.
    pg_get_viewdef,
    pg_get_ruledef,
-   pg_get_indexdef(),
-   pg_get_triggerdef(), and
+   pg_get_indexdef,
+   pg_get_triggerdef, and
    pg_get_constraintdef respectively
    reconstruct the creating command for a view, rule, index, or
    constraint.  (Note that this is a decompiled reconstruction, not
@@ -6872,9 +6882,9 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
        get CREATE INDEX command for index
       
       
-       pg_get_triggerdef(triggerOID)
+       pg_get_triggerdef(trigger_oid)
        text
-       Get CREATE [ CONSTRAINT ] TRIGGER command for trigger
+       get CREATE [ CONSTRAINT ] TRIGGER command for trigger
       
       
        pg_get_constraintdef(constraint_oid)