In what partition design do you need a trigger per child table? You only need to add partitions to the trigger on the parent table, or at the branches if you ha

In what partition design do you need a trigger per child table? You only need to add partitions to the trigger on the parent table, or at the branches if you have multiple hierarchy levels. I run a Postgres instance that partitions daily (for reasons of space management). When creating the partitions in advance, it is easy enough to alter the trigger (or a function called by the trigger) in the same script that creates the tables. DDL via copy-edit-paste is just asking for problems anyway. Those operations should be automated.