From 0252dd434bb9ab2487cd37a93912d19ca1ef5149 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc" Date: Sun, 24 Sep 2023 16:03:29 -0500 Subject: [PATCH v2 03/11] Better section heading for plpgsql exception trapping The docs seem to use "error" and "exception" interchangeably, perhaps 50% each. But they never say that the are the same thing, and in the larger world they are not. Errors tend to be something that drop on the floor and usually halt execution whereas exceptions can be trapped and give the programmer more control over the flow of the program. "Trapping Errors" is not a good section title for these reasons, and because when it comes to programmatically raising errors in Pl/PgSQL you don't, you raise exceptions. The current section heading does not stand out in a scan of the table of contents when you're looking for exception handling, IMHO. "Error Handling and Exception Trapping" is a little long but it does accurately reflect that the section is about how Pl/PgSQL behaves under error conditions and how the programmer can trap exceptions and affect the program's flow of control. The "Exception" does not stand out as much as I'd like on a scan of the table of contents, but enough. I left "Error" in the title since the word "error" is used so frequently in the docs, and the section is also about what happens when there is any sort of PG error, not just those raised in user code. --- doc/src/sgml/plpgsql.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index 874578265e..646d0305eb 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -2756,7 +2756,7 @@ NOTICE: row = {10,11,12} - Trapping Errors + Error Handling and Exception Trapping exceptions -- 2.30.2