Greg Nancarrow <[email protected]> writes:
> On Fri, Mar 12, 2021 at 5:00 AM Tom Lane <[email protected]> wrote:
>> BTW, having special logic for FK triggers in
>> target_rel_trigger_max_parallel_hazard seems quite loony to me.
>> Why isn't that handled by setting appropriate proparallel values
>> for those trigger functions?
> ... and also attached a patch to update the code for this issue.
Hm, what I was expecting to see is that RI_FKey_check_ins and
RI_FKey_check_upd get marked as proparallel = 'r' and the remainder
get marked as proparallel = 'u'. Remember that the default for
builtin functions is proparallel = 's', but surely that's wrong
for triggers that can propagate updates to other tables?
regards, tom lane
