Trigger execution order in PostgreSQL - Time & Space Complexity

Time Complexity: Trigger execution order

O(t x n)

Understanding Time Complexity

When multiple triggers run on the same table event, the order they execute affects performance.

We want to understand how the number of triggers impacts execution time.

Scenario Under Consideration

Analyze the time complexity of this trigger setup.

CREATE TABLE orders (id SERIAL PRIMARY KEY, amount INT);

CREATE FUNCTION trg_before_insert() RETURNS trigger AS $$
BEGIN
  -- some logic
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

CREATE TRIGGER before_insert_1 BEFORE INSERT ON orders
FOR EACH ROW EXECUTE FUNCTION trg_before_insert();

CREATE TRIGGER before_insert_2 BEFORE INSERT ON orders
FOR EACH ROW EXECUTE FUNCTION trg_before_insert();

-- Assume multiple triggers like this are defined

This code creates multiple BEFORE INSERT triggers on the same table, each running some logic for every new row.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Each trigger function runs once per inserted row.
• How many times: Number of triggers x number of inserted rows.

How Execution Grows With Input

As you add more triggers or insert more rows, the total work grows.

Input Size (n)	Approx. Operations
10 rows, 2 triggers	20 trigger executions
100 rows, 2 triggers	200 trigger executions
1000 rows, 2 triggers	2000 trigger executions

Pattern observation: Total executions grow proportionally with rows and triggers.

Final Time Complexity

Time Complexity: O(t x n)

This means the time grows linearly with both the number of triggers (t) and the number of rows inserted (n).

Common Mistake

[X] Wrong: "Adding more triggers won't affect performance much because they run quickly."

[OK] Correct: Each trigger runs for every row, so more triggers multiply the work and slow down inserts noticeably.

Interview Connect

Understanding how trigger execution scales helps you design efficient database logic and avoid slowdowns in real projects.

Self-Check

What if triggers were defined as FOR EACH STATEMENT instead of FOR EACH ROW? How would the time complexity change?

Practice

1. In PostgreSQL, when multiple triggers are set for the same event and timing on a table, how does the database decide the order in which to execute them?

easy

A. It executes triggers based on the size of the table.

B. It executes triggers randomly.

C. It executes triggers in the order they were created.

D. It executes triggers in alphabetical order by their trigger names.

Solution

1. Step 1: Understand trigger execution timing

   PostgreSQL runs triggers automatically on table events like INSERT, UPDATE, or DELETE.

2. Step 2: Identify execution order rule

   When multiple triggers exist for the same event and timing, PostgreSQL executes them in the order they were created.

3. Final Answer:

   It executes triggers in the order they were created. -> Option C

4. Quick Check:

   Trigger order = creation order [OK]

Hint: Remember: PostgreSQL orders triggers by creation order [OK]

Common Mistakes:

• Assuming triggers run in alphabetical order
• Thinking triggers run randomly
• Believing trigger order depends on table size

2. Which of the following is the correct syntax to create a BEFORE INSERT trigger named alpha_trigger on a table users in PostgreSQL?

easy

A. CREATE TRIGGER alpha_trigger BEFORE INSERT ON users FOR EACH ROW EXECUTE FUNCTION func_name();

B. CREATE TRIGGER alpha_trigger ON users BEFORE INSERT EXECUTE FUNCTION func_name();

C. CREATE TRIGGER alpha_trigger BEFORE INSERT EXECUTE FUNCTION func_name() ON users;

D. CREATE TRIGGER alpha_trigger BEFORE INSERT ON users EXECUTE PROCEDURE func_name();

Solution

1. Step 1: Recall correct CREATE TRIGGER syntax

   The correct syntax is: CREATE TRIGGER name BEFORE event ON table FOR EACH ROW EXECUTE FUNCTION function_name();

2. Step 2: Check each option

   CREATE TRIGGER alpha_trigger BEFORE INSERT ON users FOR EACH ROW EXECUTE FUNCTION func_name(); matches the correct syntax exactly. CREATE TRIGGER alpha_trigger BEFORE INSERT ON users EXECUTE PROCEDURE func_name(); uses EXECUTE PROCEDURE which is deprecated in modern PostgreSQL versions.

3. Final Answer:

   CREATE TRIGGER alpha_trigger BEFORE INSERT ON users FOR EACH ROW EXECUTE FUNCTION func_name(); -> Option A

4. Quick Check:

   Correct syntax uses EXECUTE FUNCTION and ON table [OK]

Hint: Use EXECUTE FUNCTION and ON table in CREATE TRIGGER [OK]

Common Mistakes:

• Using EXECUTE PROCEDURE instead of EXECUTE FUNCTION
• Placing ON table after EXECUTE FUNCTION
• Omitting FOR EACH ROW clause

3. Given two triggers on table orders: alpha_trigger and beta_trigger, both BEFORE INSERT triggers. Which trigger runs first when a new row is inserted?

medium

A. alpha_trigger runs first because 'a' comes before 'b' alphabetically.

B. beta_trigger runs first because 'b' comes before 'a' alphabetically.

C. Both triggers run simultaneously.

D. The trigger created last runs first.

Solution

1. Step 1: Identify trigger names and order

   Triggers are named alpha_trigger and beta_trigger. Alphabetically, 'alpha' comes before 'beta'.

2. Step 2: Apply PostgreSQL trigger execution order

   PostgreSQL executes triggers in the order they were created for the same event and timing, not alphabetical order.

3. Final Answer:

   beta_trigger runs first because it was created before alpha_trigger. -> Option B

4. Quick Check:

   Trigger order = creation order [OK]

Hint: Trigger execution order depends on creation order, not alphabetical [OK]

Common Mistakes:

• Assuming alphabetical order matters
• Thinking triggers run simultaneously
• Confusing creation order

4. You have two AFTER UPDATE triggers on table products: zeta_trigger and alpha_trigger. You want zeta_trigger to run before alpha_trigger. What is the problem with this setup?

medium

A. Triggers run in reverse alphabetical order, so zeta_trigger runs first as desired.

B. PostgreSQL does not support multiple triggers on the same event.

C. You must rename triggers to numbers to control order.

D. PostgreSQL runs triggers alphabetically, so alpha_trigger runs before zeta_trigger regardless of creation order.

Solution

1. Step 1: Understand trigger execution order

   PostgreSQL executes multiple triggers for the same event and timing in the order they were created.

2. Step 2: Analyze the trigger names

   Trigger names do not affect execution order; creation order does. So the trigger created first runs first.

3. Final Answer:

   PostgreSQL runs triggers in creation order, so alpha_trigger runs before zeta_trigger if created first. -> Option D

4. Quick Check:

   Trigger order = creation order [OK]

Hint: Creation order controls trigger execution, not alphabetical order [OK]

Common Mistakes:

• Assuming creation order controls execution
• Believing reverse alphabetical order applies
• Thinking trigger renaming is unnecessary

5. You have three BEFORE DELETE triggers on table customers: clean_up, archive, and notify. You want archive to run first, then clean_up, then notify. How should you rename the triggers to ensure this execution order?

hard

A. No renaming needed; PostgreSQL runs triggers in creation order.

B. Rename triggers to notify, clean_up, archive.

C. Rename triggers to a_archive, b_clean_up, c_notify.

D. Rename triggers to 1_archive, 2_clean_up, 3_notify.

Solution

1. Step 1: Understand trigger execution order

   PostgreSQL executes triggers in the order they were created for the same event and timing.

2. Step 2: Renaming triggers does not affect execution order

   Renaming triggers does not change execution order; only creation order matters.

3. Final Answer:

   No renaming needed; PostgreSQL runs triggers in creation order. -> Option A

4. Quick Check:

   Trigger order = creation order [OK]

Hint: Trigger execution order depends on creation order, not name [OK]

Common Mistakes:

• Assuming alphabetical order controls execution
• Believing numeric or alphabetical prefixes affect order
• Not understanding creation order importance