summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-11-02 07:33:02 +0900
committerMichael Paquier <michael@paquier.xyz>2023-11-02 07:33:35 +0900
commitaa0246ccf5bb6b306777463ff4c4a7c49f38d058 (patch)
tree8b17a13cdd3ac6264aa072131c55a816e62a2609
parent3c9e5cea219aa60cb44c7315369df16358c915bb (diff)
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
-rw-r--r--doc/src/sgml/plpgsql.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index c46e60eb278..998d71029f1 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3787,7 +3787,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>