Fix potential NULL-pointer dereference.

Commit 2781b4bea7db357be59f9a5fd73ca1eb12ff5a79 arranged to defer
the setup of after-trigger-related data structures, but
AfterTriggerPendingOnRel didn't get the memo.

diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c
index 31a5411140d613f7f2712eb4c478e06316d21cea..ebccfea3d7c347dfbfc683e6e4b646d76092d3aa 100644 (file)
--- a/src/backend/commands/trigger.c
+++ b/src/backend/commands/trigger.c
@@ -4776,7 +4776,7 @@ AfterTriggerPendingOnRel(Oid relid)
     * if TRUNCATE/etc is executed by a function or trigger within an updating
     * query on the same relation, which is pretty perverse, but let's check.
     */
-   for (depth = 0; depth <= afterTriggers.query_depth; depth++)
+   for (depth = 0; depth <= afterTriggers.query_depth && depth < afterTriggers.maxquerydepth; depth++)
    {
        for_each_event_chunk(event, chunk, afterTriggers.query_stack[depth])
        {