postgres.git / summary / log / commit / refs

commit    e55e4c9ced485b44be9e100bbe54546a3272ddae
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Tue Nov 09 14:00:56 2010 +0000
First released in: 9.1.0, 9.0.2

    plpython has plpy.Error instead of plpy.ERROR
    
    Author: Marti Raudsepp <marti@juffo.org>


 doc/src/sgml/plpython.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index aa7804d9bb3..daefc583f3b 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -954,8 +954,8 @@ $$ LANGUAGE plpythonu;
    <function>plpy.fatal</function> actually raise a Python exception
    which, if uncaught, propagates out to the calling query, causing
    the current transaction or subtransaction to be aborted.
-   <literal>raise plpy.ERROR(<replaceable>msg</>)</literal> and
-   <literal>raise plpy.FATAL(<replaceable>msg</>)</literal> are
+   <literal>raise plpy.Error(<replaceable>msg</>)</literal> and
+   <literal>raise plpy.Fatal(<replaceable>msg</>)</literal> are
    equivalent to calling
    <function>plpy.error</function> and
    <function>plpy.fatal</function>, respectively.


[parent: c6c67505e4b7]