On Mon, Jun 4, 2018 at 2:40 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > I think, in general, that we should try to pick semantics that make a > > partitioned table behave like an unpartitioned table, provided that > > all triggers are defined on the partitioned table itself. > > Well, then we lose the property Alvaro wanted, namely that if an > application chooses to insert directly into a partition, that's > just an optimization that changes no behavior (as long as it picked > the right partition). Maybe this can be dodged by propagating > parent trigger definitions to the children, but it's going to be > complicated I'm afraid. >
Can we give the user the option - adding a before trigger to the partitioned table forces one to forgo the ability to directly insert into the partitions? David J.
