doc: Improve search_path mentions in index
authorPeter Eisentraut
Fri, 14 Dec 2012 04:00:42 +0000 (23:00 -0500)
committerPeter Eisentraut
Fri, 14 Dec 2012 04:00:42 +0000 (23:00 -0500)
Karl O. Pinc

doc/src/sgml/ddl.sgml
doc/src/sgml/func.sgml
doc/src/sgml/ref/create_function.sgml

index d6e5d646ee462cb7320df9ef3b17d06de93d55f8..207de9b125994c2c08e3e4d9de4b9da62abc6686 100644 (file)
@@ -1735,7 +1735,7 @@ CREATE TABLE public.products ( ... );
    
 
    
-    search_path
+    search_path configuration parameter
    
 
    
index c8a2a149fa8c66bc352764406246ba9123d87f14..e184d99626e6a86e36bebc45de2dd20ffd94652a 100644 (file)
@@ -13507,6 +13507,11 @@ SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
 
   
 
+   
+    search path
+    object visibility
+   
+
    
     Schema Visibility Inquiry Functions
     
index fee6f53ba2437ced8b9734bfb1860b54661f0972..4ac5bdaf65ff3b3266af961cdfa4aee3ce1b1eec 100644 (file)
@@ -673,6 +673,11 @@ SELECT * FROM dup(42);
  
   Writing <literal>SECURITY DEFINER</literal> Functions Safely
 
+  
+   search_path configuration parameter
+   use in securing functions
+  
+
    
     Because a SECURITY DEFINER function is executed
     with the privileges of the user that created it, care is needed to