Trigger execution order in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a trigger in PostgreSQL?

A trigger is a special procedure that automatically runs when certain events happen in the database, like inserting, updating, or deleting data.

intermediate

When multiple triggers are set on the same event, how does PostgreSQL decide which trigger runs first?

PostgreSQL executes BEFORE triggers in alphabetical order by their names before the event, and AFTER triggers in alphabetical order by their names after the event.

beginner

What is the difference between BEFORE and AFTER triggers in execution order?

BEFORE triggers run before the database action happens, and they run in alphabetical order. AFTER triggers run after the action and run in alphabetical order.

intermediate

Can you control the order of trigger execution in PostgreSQL?

You can control the order by naming triggers carefully because PostgreSQL orders both BEFORE and AFTER triggers alphabetically by name.

beginner

What happens if two triggers have the same name in PostgreSQL?

PostgreSQL does not allow two triggers with the same name on the same table. Each trigger must have a unique name per table.

In PostgreSQL, which triggers run first on an INSERT event?

A BEFORE triggers in alphabetical order

B AFTER triggers in alphabetical order

C BEFORE triggers in reverse alphabetical order

D AFTER triggers in reverse alphabetical order

BEFORE triggers run before the event and are executed in alphabetical order by their names.

How are AFTER triggers executed in PostgreSQL?

A Randomly

B In reverse alphabetical order

C In the order they were created

D In alphabetical order

AFTER triggers run after the event and are executed in alphabetical order by their names.

Can you have two triggers with the same name on the same table and event in PostgreSQL?

A Yes, if they are BEFORE and AFTER triggers

B No, trigger names must be unique per table

C Yes, if they have different functions

D Yes, if they are on different columns

Trigger names must be unique for each table.

If you want a trigger to run last among BEFORE triggers, how should you name it?

A Start its name with 'Z'

B Use numbers in the name

C Name does not affect order

D Start its name with 'A'

BEFORE triggers run in alphabetical order, so a name starting with 'Z' will run last.

Which of these is true about trigger execution order in PostgreSQL?

A AFTER triggers run before BEFORE triggers

B BEFORE triggers run after the event

C BEFORE triggers run before the event in alphabetical order

D Trigger execution order is random

BEFORE triggers run before the event and are executed in alphabetical order.

Explain how PostgreSQL decides the order of trigger execution when multiple triggers exist on the same event.

Think about the timing (before or after) and the alphabetical order of trigger names.

Describe how you can control the execution order of triggers in PostgreSQL.

Focus on naming triggers to influence their order.

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