postgres.git / summary / log / commit / refs

commit    52a105eff2ba2e8154e5a25ae69603ef421b8804
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Wed Nov 01 22:33:02 2023 +0000
First released in: 17.0, 11.22, 12.17, 13.13, 14.10, 15.5, 16.1

    doc: Replace reference to ERRCODE_RAISE_EXCEPTION by "raise_exception"
    
    This part of the documentation refers to exceptions as handled by
    PL/pgSQL, and using the internal error code is confusing.
    
    Per thinko in 66bde49d96a9.
    
    Reported-by: Euler Taveira, Bruce Momjian
    Discussion: https://postgr.es/m/ZUEUnLevXyW7DlCs@momjian.us
    Backpatch-through: 11


 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 8017ba392a4..aecf8ffd846 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3903,7 +3903,7 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
    <para>
     If no condition name nor SQLSTATE is specified in a
     <command>RAISE EXCEPTION</command> command, the default is to use
-    <literal>ERRCODE_RAISE_EXCEPTION</literal> (<literal>P0001</literal>).
+    <literal>raise_exception</literal> (<literal>P0001</literal>).
     If no message text is specified, the default is to use the condition
     name or SQLSTATE as message text.
    </para>


[parent: b3dd43db1a3b]