41.9. Errors and Messages | ||||
---|---|---|---|---|
Prev | Up | Chapter 41. PL/pgSQL —SQL Procedural Language | Home | Next |
41.9. Errors and Messages#
41.9.1. Reporting Errors and Messages#
Use theRAISE
statement to report messages and raise errors.
RAISE [level
] 'format
' [,expression
[, ...]] [ USINGoption
=expression
[, ...]];RAISE [level
]condition_name
[ USINGoption
=expression
[, ...]];RAISE [level
] SQLSTATE 'sqlstate
' [ USINGoption
=expression
[, ...]];RAISE [level
] USINGoption
=expression
[, ...];RAISE ;
Thelevel
option specifies the error severity. Allowed levels areDEBUG
,LOG
,INFO
,NOTICE
,WARNING
, andEXCEPTION
, withEXCEPTION
being the default.EXCEPTION
raises an error (which normally aborts the current transaction); the other levels only generate messages of different priority levels. Whether messages of a particular priority are reported to the client, written to the server log, or both is controlled by thelog_min_messages andclient_min_messages configuration variables. SeeChapter 19 for more information.
Afterlevel
if any, you can specify aformat
string (which must be a simple string literal, not an expression). The format string specifies the error message text to be reported. The format string can be followed by optional argument expressions to be inserted into the message. Inside the format string,%
is replaced by the string representation of the next optional argument's value. Write%%
to emit a literal%
. The number of arguments must match the number of%
placeholders in the format string, or an error is raised during the compilation of the function.
In this example, the value ofv_job_id
will replace the%
in the string:
RAISE NOTICE 'Calling cs_create_job(%)', v_job_id;
You can attach additional information to the error report by writingUSING
followed byoption
=expression
items. Eachexpression
can be any string-valued expression. The allowedoption
key words are:
MESSAGE
#Sets the error message text. This option can't be used in the form of
RAISE
that includes a format string beforeUSING
.DETAIL
#Supplies an error detail message.
HINT
#Supplies a hint message.
ERRCODE
#Specifies the error code (SQLSTATE) to report, either by condition name, as shown inAppendix A, or directly as a five-character SQLSTATE code.
COLUMN
CONSTRAINT
DATATYPE
TABLE
SCHEMA
#Supplies the name of a related object.
This example will abort the transaction with the given error message and hint:
RAISE EXCEPTION 'Nonexistent ID --> %', user_id USING HINT = 'Please check your user ID';
These two examples show equivalent ways of setting the SQLSTATE:
RAISE 'Duplicate user ID: %', user_id USING ERRCODE = 'unique_violation';RAISE 'Duplicate user ID: %', user_id USING ERRCODE = '23505';
There is a secondRAISE
syntax in which the main argument is the condition name or SQLSTATE to be reported, for example:
RAISE division_by_zero;RAISE SQLSTATE '22012';
In this syntax,USING
can be used to supply a custom error message, detail, or hint. Another way to do the earlier example is
RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
Still another variant is to writeRAISE USING
orRAISE
and put everything else into thelevel
USINGUSING
list.
The last variant ofRAISE
has no parameters at all. This form can only be used inside aBEGIN
block'sEXCEPTION
clause; it causes the error currently being handled to be re-thrown.
Note
BeforePostgreSQL 9.1,RAISE
without parameters was interpreted as re-throwing the error from the block containing the active exception handler. Thus anEXCEPTION
clause nested within that handler could not catch it, even if theRAISE
was within the nestedEXCEPTION
clause's block. This was deemed surprising as well as being incompatible with Oracle's PL/SQL.
If no condition name nor SQLSTATE is specified in aRAISE EXCEPTION
command, the default is to useraise_exception
(P0001
). If no message text is specified, the default is to use the condition name or SQLSTATE as message text.
Note
When specifying an error code by SQLSTATE code, you are not limited to the predefined error codes, but can select any error code consisting of five digits and/or upper-case ASCII letters, other than00000
. It is recommended that you avoid throwing error codes that end in three zeroes, because these are category codes and can only be trapped by trapping the whole category.
41.9.2. Checking Assertions#
TheASSERT
statement is a convenient shorthand for inserting debugging checks intoPL/pgSQL functions.
ASSERTcondition
[ ,message
];
Thecondition
is a Boolean expression that is expected to always evaluate to true; if it does, theASSERT
statement does nothing further. If the result is false or null, then anASSERT_FAILURE
exception is raised. (If an error occurs while evaluating thecondition
, it is reported as a normal error.)
If the optionalmessage
is provided, it is an expression whose result (if not null) replaces the default error message text“assertion failed”, should thecondition
fail. Themessage
expression is not evaluated in the normal case where the assertion succeeds.
Testing of assertions can be enabled or disabled via the configuration parameterplpgsql.check_asserts
, which takes a Boolean value; the default ison
. If this parameter isoff
thenASSERT
statements do nothing.
Note thatASSERT
is meant for detecting program bugs, not for reporting ordinary error conditions. Use theRAISE
statement, described above, for that.