diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-01-03 12:22:00 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-01-03 12:22:00 -0500 |
| commit | 490dee74286c4910971353ee38885529888e0f1e (patch) | |
| tree | 7011dc03fd9f25211256558df5d80257568075ed | |
| parent | 8d4e8b746815505c3b808ab96674ec2e140afc56 (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.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml index 0ca80fb1a15..68cefbb10bc 100644 --- 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; </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 |