From 73bc5218df0330a4beb737f497fa8d7b337c9f90 Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Tue, 9 Nov 2010 11:00:56 -0300
Subject: [PATCH] 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 6eb884e0dc..9fc8808776 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.
-- 
2.40.0