Update docs for new stored procedure error levels.

diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
index 8fb6f36074a2959ad6091ca598f45c0383d05506..c04ff95d929d100b8866c99b70f93c5f6a8a8849 100644 (file)
--- a/doc/src/sgml/plperl.sgml
+++ b/doc/src/sgml/plperl.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -278,13 +278,12 @@ CREATE FUNCTION badfunc() RETURNS integer AS '
       elog level, msg
       
        
-   Emit a log or error message. Possible levels are DEBUG,
-   NOTICE, and ERROR.
-   DEBUG and NOTICE simply emit the given message
-   into the postmaster log (and send it to the client too, in the case of
-   NOTICE).  ERROR raises an error condition:
-   further execution of the function is abandoned, and the current
-   transaction is aborted.
+   Emit a log or error message. Possible levels are
+   DEBUG, LOG, INFO,
+   NOTICE, WARNING, and ERROR.
+   ERROR raises an error condition: further execution
+   of the function is abandoned, and the current transaction is
+   aborted.
        
       
      

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index 768c26b569efd6ca4e62c6d4120cd8ea6766c1db..e0840c822a3efc562542a3250636abf6aa591fa2 100644 (file)
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  PL/Python - Python Procedural Language
@@ -150,12 +150,14 @@ def __plpython_procedure_myfunc_23456():
    this module are available to you in the Python code as
    plpy.foo.  At present
    plpy implements the functions
-   plpy.error("msg"),
-   plpy.fatal("msg"),
-   plpy.debug("msg"), and
-   plpy.notice("msg").  They are mostly equivalent
-   to calling elog(LEVEL, "msg"),
-   where LEVEL is DEBUG, ERROR, FATAL or NOTICE.
+   plpy.debug("msg"), 
+   plpy.log("msg"),
+   plpy.info("msg"),
+   plpy.notice("msg"),
+   plpy.warning("msg"),
+   plpy.error("msg"), and
+   plpy.fatal("msg").  They are mostly equivalent
+   to calling elog(LEVEL, "msg").
    plpy.error and plpy.fatal
    actually raise a Python exception which, if uncaught, causes the
    PL/Python module to call elog(ERROR, msg) when

diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml
index 395861a81fc443857e07eb9b99135a1c5cb55fff..af00cb733255ac02914d61b4c360a1ea4c0c3193 100644 (file)
--- a/doc/src/sgml/pltcl.sgml
+++ b/doc/src/sgml/pltcl.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -441,16 +441,17 @@ SELECT 'doesn''t' AS ret
       elog level msg
       
        
-   Emit a log or error message. Possible levels are DEBUG,
-   NOTICE, ERROR, and FATAL.
-   DEBUG and NOTICE simply emit the given message
-   into the postmaster log (and send it to the client too, in the case of
-   NOTICE).  ERROR raises an error condition:
-   further execution of the function is abandoned, and the current
-   transaction is aborted.  FATAL aborts the transaction and
-   causes the current backend to shut down (there is probably no good
-   reason to use this error level in PL/Tcl functions, but it's provided
-   for completeness).
+   Emit a log or error message. Possible levels are
+   DEBUG, LOG, INFO,
+   NOTICE, WARNING, ERROR, and
+   FATAL. Most simply emit the given message just like
+   the elog backend C function. ERROR
+   raises an error condition: further execution of the function is
+   abandoned, and the current transaction is aborted.
+   FATAL aborts the transaction and causes the current
+   backend to shut down (there is probably no good reason to use
+   this error level in PL/Tcl functions, but it's provided for
+   completeness).