Gavin Sherry <[EMAIL PROTECTED]> writes:
> Now, if for all the triggers on the base relation, !trigger->tgenabled is
> true, then newtuple will always be NULL.
Hmm ... seems like the all-triggers-disabled case should act the same as
the no-triggers-at-all case, which this doesn't seem to do. It does
look broken but this doesn't seem like the correct fix.
>> Also, if there is a point, why are we changing only one of the
>> several ExecFOOTriggers functions?
> Because only BEFORE DELETE worries about trigger procedures returning
> NULL, from memory.
Do I have to do more than raise my eyebrow here?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
