summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2024-01-03 17:22:00 +0000
committerTom Lane2024-01-03 17:22:00 +0000
commit76ba8a8b631454ad06b6d4dd186ef2a739f0f7ce (patch)
treee922db649962d59f9b275ce55e641ca933a7c8de
parentdffde5bf16a590543a35bedffc936a33686651d4 (diff)
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
-rw-r--r--doc/src/sgml/plpython.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index e05e607aba0..e5d51d6e9f5 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1175,7 +1175,7 @@ plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
plpy.execute(plan, [result])
$$ LANGUAGE plpython3u;
</programlisting>
- Note that the use of <literal>try/catch</literal> is still
+ Note that the use of <literal>try</literal>/<literal>except</literal> 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 <productname>PostgreSQL</productname> error, so that the