Trigger execution order in PostgreSQL - Step-by-Step Execution

Concept Flow - Trigger execution order

Event occurs on table

↓

Check for BEFORE triggers

Yes↓

Execute BEFORE triggers in defined order

↓

Perform the actual operation (INSERT/UPDATE/DELETE)

↓

Check for AFTER triggers

Yes↓

Execute AFTER triggers in defined order

↓

Operation completes

When a table event happens, PostgreSQL runs BEFORE triggers first in order, then the main operation, then AFTER triggers in order.

Execution Sample

PostgreSQL

CREATE TRIGGER trg_before_1 BEFORE INSERT ON employees FOR EACH ROW EXECUTE FUNCTION func_before_1();
CREATE TRIGGER trg_before_2 BEFORE INSERT ON employees FOR EACH ROW EXECUTE FUNCTION func_before_2();
CREATE TRIGGER trg_after_1 AFTER INSERT ON employees FOR EACH ROW EXECUTE FUNCTION func_after_1();
INSERT INTO employees (name) VALUES ('Alice');

This code sets two BEFORE and one AFTER insert triggers on employees, then inserts a row to show trigger execution order.

Execution Table

Step	Trigger/Event	Action	Order	Output/Effect
1	INSERT on employees	Event starts	-	Waiting for triggers
2	BEFORE INSERT trg_before_1	Execute func_before_1()	1	Before trigger 1 runs
3	BEFORE INSERT trg_before_2	Execute func_before_2()	2	Before trigger 2 runs
4	INSERT operation	Insert row ('Alice')	-	Row inserted
5	AFTER INSERT trg_after_1	Execute func_after_1()	1	After trigger runs
6	End	Operation completes	-	Insert transaction done

💡 All triggers executed in order; operation completes successfully.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Row Data	N/A	Unchanged	Unchanged	Inserted ('Alice')	Unchanged	Inserted ('Alice')
Trigger State	None	BEFORE 1 executed	BEFORE 2 executed	Operation done	AFTER 1 executed	All triggers done

Key Moments - 3 Insights

Why do BEFORE triggers run before the actual insert operation?

BEFORE triggers run first to allow modification or validation of data before it is inserted, as shown in execution_table steps 2 and 3 before step 4.

Can AFTER triggers modify the inserted row?

No, AFTER triggers run after the operation completes, so they cannot change the inserted row but can perform actions like logging, as seen in step 5.

What determines the order of multiple triggers of the same timing?

Triggers execute in the order they were created, so trg_before_1 runs before trg_before_2 as shown in steps 2 and 3.

Visual Quiz - 3 Questions

Look at the execution_table, which step shows the actual row insertion?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Check the 'Action' column for 'Insert row' in execution_table.

At which step does the second BEFORE trigger execute?

A Step 3

B Step 5

C Step 2

D Step 4

💡 Hint

Look for 'BEFORE INSERT trg_before_2' in execution_table step 3.

If trg_before_1 was created after trg_before_2, which step would it execute in?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Trigger order depends on creation order; see key_moments about execution order.

Concept Snapshot

Trigger Execution Order in PostgreSQL:
- BEFORE triggers run first, in creation order.
- Then the main operation (INSERT/UPDATE/DELETE) happens.
- AFTER triggers run last, also in creation order.
- Multiple triggers of same timing run sequentially.
- BEFORE triggers can modify data; AFTER triggers cannot.

Full Transcript

When a database event like INSERT happens on a table, PostgreSQL first checks for any BEFORE triggers defined for that event. It executes these BEFORE triggers in the order they were created. After all BEFORE triggers run, the actual operation (such as inserting the row) is performed. Then PostgreSQL checks for any AFTER triggers for that event and executes them in creation order. This sequence ensures that BEFORE triggers can modify or validate data before the operation, and AFTER triggers can perform actions after the operation completes. The execution table shows each step with triggers running before and after the insert operation, demonstrating the order clearly.

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