Debugging

Syntax

RAISE has the following five syntax formats:

Figure 1 raise_format::=

Figure 2 raise_condition::=

Figure 3 raise_sqlstate::=

Figure 4 raise_option::=

Figure 5 raise::=

Parameter description:

• The level option is used to specify the error level, that is, DEBUG, LOG, INFO, NOTICE, WARNING, or EXCEPTION (default). EXCEPTION throws an error that normally terminates the current transaction and the others only generate information at their levels. The GUC parameters log_min_messages and client_min_messages control whether the error messages of specific levels are reported to the client and are written to the server log.
• format: specifies the error message text to be reported, a format string. The format string can be appended with an expression for insertion to the message text. In a format string, % is replaced by the parameter value attached to format and %% is used to print %. For example:

  --v_job_id replaces % in the string.
  RAISE NOTICE 'Calling cs_create_job(%)',v_job_id;

• option = expression: inserts additional information to an error report. The keyword option can be MESSAGE, DETAIL, HINT, or ERRCODE, and each expression can be any string.
  • MESSAGE: specifies the error message text. This option cannot be used in a RAISE statement that contains a format character string in front of USING.
  • DETAIL: specifies detailed information of an error.
  • HINT: prints hint information.
  • ERRCODE: designates an error code (SQLSTATE) to a report. A condition name or a five-character SQLSTATE error code can be used.
• condition_name: specifies the condition name corresponding to the error code.
• sqlstate: specifies the error code.

If neither a condition name nor an SQLSTATE is specified in the RAISE EXCEPTION command, the RAISE EXCEPTION (P0001) is used by default. If no message text is specified, the condition name or SQLSTATE is used as the message text by default.

• If the SQLSTATE specifies an error code, the error code is not limited to a defined error code. It can be any error code containing five digits or ASCII uppercase rather than 00000. Do not use an error code ended with three zeros because such error codes are category codes and can be captured by the whole category.
• In O-compatible mode, SQLCODE is equivalent to SQLSTATE.

The syntax described in Figure 5 does not append any parameter. This form is used only for the EXCEPTION statement in a BEGIN block so that the error can be re-processed.

Examples

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

CREATE OR REPLACE PROCEDURE proc_raise1(user_id in integer)
AS 
BEGIN 
RAISE EXCEPTION 'Noexistence ID --> %',user_id USING HINT = 'Please check your user ID'; 
END; 
/

call proc_raise1(300011);

-- Execution result
ERROR:  Noexistence ID --> 300011
HINT:  Please check your user ID

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

CREATE OR REPLACE PROCEDURE proc_raise2(user_id in integer)
AS 
BEGIN 
RAISE 'Duplicate user ID: %',user_id USING ERRCODE = 'unique_violation'; 
END; 
/

\set VERBOSITY verbose
call proc_raise2(300011);

-- Execution result
ERROR:  Duplicate user ID: 300011
SQLSTATE: 23505

If the main parameter is a condition name or SQLSTATE, the following applies:

RAISE division_by_zero;

RAISE SQLSTATE '22012';

For example:

CREATE OR REPLACE PROCEDURE division(div in integer, dividend in integer) 
AS 
DECLARE 
res int; 
    BEGIN 
    IF dividend=0 THEN 
        RAISE division_by_zero; 
        RETURN; 
    ELSE 
        res := div/dividend; 
        RAISE INFO 'division result: %', res;
        RETURN; 
    END IF; 
    END; 
/
call division(3,0);

-- Execution result
ERROR:  division_by_zero

1

RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;