RAISE for notices and exceptions in PostgreSQL - Time & Space Complexity

Time Complexity: RAISE for notices and exceptions

O(n)

Understanding Time Complexity

When using RAISE statements in PostgreSQL, it is important to understand how often these messages are triggered during query execution.

We want to know how the number of RAISE calls grows as the input data grows.

Scenario Under Consideration

Analyze the time complexity of the following PL/pgSQL block using RAISE NOTICE inside a loop.

DO $$
DECLARE
  rec RECORD;
BEGIN
  FOR rec IN SELECT id FROM users LOOP
    RAISE NOTICE 'Processing user id: %', rec.id;
  END LOOP;
END $$;

This code loops over all users and raises a notice for each user processed.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each row in the users table.
• How many times: Once for every user in the table.

How Execution Grows With Input

Each user causes one RAISE NOTICE call, so the total calls grow directly with the number of users.

Input Size (n)	Approx. Operations
10	10 RAISE calls
100	100 RAISE calls
1000	1000 RAISE calls

Pattern observation: The number of RAISE calls increases one-to-one with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to execute grows linearly as the number of users grows.

Common Mistake

[X] Wrong: "RAISE statements run only once regardless of input size."

[OK] Correct: Because RAISE inside a loop runs every time the loop runs, so it scales with the number of rows processed.

Interview Connect

Understanding how RAISE statements affect performance helps you write clear and efficient database code, a useful skill in real projects and interviews.

Self-Check

What if we moved the RAISE statement outside the loop? How would the time complexity change?

Practice

1. What does the RAISE NOTICE statement do in PostgreSQL?

easy

A. It silently logs a message without showing it to the user.

B. It stops the code execution and returns an error.

C. It sends a message to the client but continues running the code.

D. It restarts the current transaction automatically.

Solution

1. Step 1: Understand RAISE NOTICE behavior

   RAISE NOTICE sends an informational message to the client but does not stop the execution.

2. Step 2: Compare with other RAISE levels

   Unlike EXCEPTION, which stops execution, NOTICE only shows a message and continues.

3. Final Answer:

   It sends a message to the client but continues running the code. -> Option C

4. Quick Check:

   RAISE NOTICE = message without stopping [OK]

Hint: NOTICE shows messages but never stops code [OK]

Common Mistakes:

• Confusing NOTICE with EXCEPTION stopping code
• Thinking NOTICE hides messages
• Assuming NOTICE restarts transactions

2. Which of the following is the correct syntax to raise a warning message in a PostgreSQL function?

easy

A. RAISE WARNING 'This is a warning';

B. RAISE WARN 'This is a warning';

C. RAISE WARNNING 'This is a warning';

D. RAISE WARN_MSG 'This is a warning';

Solution

1. Step 1: Recall correct RAISE syntax for warnings

   The correct keyword is WARNING, not WARN or other variants.

2. Step 2: Validate syntax correctness

   RAISE WARNING 'message'; is the valid syntax to raise a warning message.

3. Final Answer:

   RAISE WARNING 'This is a warning'; -> Option A

4. Quick Check:

   RAISE WARNING = correct syntax [OK]

Hint: Use full word WARNING, not abbreviations [OK]

Common Mistakes:

• Using 'WARN' instead of 'WARNING'
• Misspelling WARNING as WARNNING
• Inventing unsupported keywords like WARN_MSG

3. Consider this PostgreSQL PL/pgSQL block:

DO $$
BEGIN
  RAISE NOTICE 'Step 1';
  RAISE WARNING 'Step 2';
  RAISE EXCEPTION 'Step 3';
  RAISE NOTICE 'Step 4';
END $$;

What will be the output?

medium

A. Step 1 and Step 4 notices print, but warning and exception are ignored.

B. All four messages print: Step 1, Step 2, Step 3, Step 4.

C. Only Step 3 error message is shown, others are ignored.

D. Step 1 (notice), Step 2 (warning), then error 'Step 3', and stops before Step 4.

Solution

1. Step 1: Trace the RAISE statements in order

   RAISE NOTICE 'Step 1' prints a message and continues.

2. Step 2: Understand RAISE WARNING and EXCEPTION effects

   RAISE WARNING 'Step 2' prints a warning and continues. RAISE EXCEPTION 'Step 3' raises an error and stops execution immediately.

3. Step 3: Check if Step 4 runs

   Since EXCEPTION stops execution, RAISE NOTICE 'Step 4' does not run.

4. Final Answer:

   Step 1 (notice), Step 2 (warning), then error 'Step 3', and stops before Step 4. -> Option D

5. Quick Check:

   EXCEPTION stops code after Step 3 [OK]

Hint: EXCEPTION stops code; notices/warnings do not [OK]

Common Mistakes:

• Assuming all messages print despite EXCEPTION
• Thinking WARNING stops execution
• Ignoring that EXCEPTION halts code immediately

4. You wrote this code inside a PostgreSQL function:

RAISE EXCEPTION 'Error: %', message;

But it causes an error: "ERROR: column "message" does not exist". What is the likely problem?

medium

A. The variable 'message' is not declared or out of scope.

B. RAISE EXCEPTION cannot use placeholders like '%'.

C. You must use RAISE WARNING instead of EXCEPTION for variables.

D. The syntax requires double quotes around 'message'.

Solution

1. Step 1: Understand the error message

   The error says column "message" does not exist, meaning 'message' is treated as a column or variable but is undefined.

2. Step 2: Check variable declaration and scope

   In PL/pgSQL, variables must be declared before use. If 'message' is not declared or out of scope, this error occurs.

3. Final Answer:

   The variable 'message' is not declared or out of scope. -> Option A

4. Quick Check:

   Undefined variable causes this error [OK]

Hint: Declare variables before using in RAISE [OK]

Common Mistakes:

• Thinking placeholders '%' are invalid
• Using RAISE WARNING instead of EXCEPTION for variables
• Adding quotes around variable names incorrectly

5. You want to write a PostgreSQL function that checks if a user age is below 18 and raises an exception with a custom message including the age. Which code snippet correctly does this?

hard

A. IF age < 18 THEN RAISE EXCEPTION 'User age % is too young' || age; END IF;

B. IF age < 18 THEN RAISE EXCEPTION 'User age % is too young', age; END IF;

C. IF age < 18 THEN RAISE EXCEPTION MESSAGE = 'User age ' || age || ' is too young'; END IF;

D. IF age < 18 THEN RAISE EXCEPTION 'User age % is too young', 'age'; END IF;

Solution

1. Step 1: Understand RAISE EXCEPTION with placeholders

   RAISE EXCEPTION supports printf-style placeholders like % and variables as arguments.

2. Step 2: Check each option's correctness

   IF age < 18 THEN RAISE EXCEPTION 'User age % is too young', age; END IF; correctly uses the % placeholder followed by the variable age as an argument.
   IF age < 18 THEN RAISE EXCEPTION 'User age % is too young' || age; END IF; incorrectly concatenates the variable to the format string, resulting in an unreplaced % and a runtime format error.
   IF age < 18 THEN RAISE EXCEPTION MESSAGE = 'User age ' || age || ' is too young'; END IF; omits the required USING keyword before MESSAGE=, causing a syntax error.
   IF age < 18 THEN RAISE EXCEPTION 'User age % is too young', 'age'; END IF; passes the string literal 'age' instead of the variable.

3. Final Answer:

   IF age < 18 THEN RAISE EXCEPTION 'User age % is too young', age; END IF; -> Option B

4. Quick Check:

   Use % and variable for dynamic messages [OK]

Hint: Use % placeholder with variable, not string 'age' [OK]

Common Mistakes:

• Concatenating strings instead of using placeholders
• Passing variable name as string instead of variable
• Using incorrect RAISE EXCEPTION syntax