pgsql: Move afterTriggerFiringDepth into AfterTriggersData

From: Amit Langote <amitlan(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Move afterTriggerFiringDepth into AfterTriggersData
Date: 2026-04-10 07:18:19
Message-ID: E1wB68B-000GRX-0G@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Move afterTriggerFiringDepth into AfterTriggersData

The static variable afterTriggerFiringDepth introduced by commit
5c54c3ed1b9 is logically part of the after-trigger state and in
hindsight should have been a field in AfterTriggersData alongside
query_depth and the other per-transaction after-trigger state.
Move it there as firing_depth. Also update its comment to
accurately reflect its sole remaining purpose: signaling to
AfterTriggerIsActive() that after-trigger firing is active.

Reviewed-by: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Discussion: https://postgr.es/m/CA+HiwqFt4NGTNk7BinOsHHM48E9zGAa852vCfGoSe1bbL=JNFQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d6e96bacd3c05f1a2c1e350d04cc450e91311299

Modified Files
--------------
src/backend/commands/trigger.c | 36 ++++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Langote 2026-04-10 09:12:37 pgsql: Add test case for same-type reordered FK columns
Previous Message Richard Guo 2026-04-10 06:51:43 pgsql: Fix var_is_nonnullable() to account for varreturningtype