Doc: Python's control flow construct is try/except not try/catch.

Very ancient thinko, dating evidently to 22690719e.
Spotted by gweatherby.

Discussion: https://postgr.es/m/170423637139.1288848.11840082988774620003@wrigleys.postgresql.org

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index 0ca80fb1a152453602264d6baf559cb341e24668..68cefbb10bcb91a12562be11e9933303ed586bfb 100644 (file)
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1323,7 +1323,7 @@ plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
 plpy.execute(plan, [result])
 $$ LANGUAGE plpythonu;
 
-    Note that the use of try/catch is still
+    Note that the use of try/except is still
     required.  Otherwise the exception would propagate to the top of
     the Python stack and would cause the whole function to abort with
     a PostgreSQL error, so that the