On Wed, Nov 25, 2009 at 11:30 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > It seems like the easiest way to resolve this without weird corner > cases is to say that we fire triggers belonging to the parent table. > The individual partition child tables either shouldn't have triggers > at all, or we should restrict the cases in which those are considered > applicable. > > As an example, what are you going to do with statement-level triggers? > Fire them for *every* child whether it receives a row or not? Doesn't > seem like the right thing.
Just the tables that get a row? I don't know, your way may be best, but it seems like tables on individual partitions might be useful in some situations. > Again, this solution presupposes an explicit concept of partitioned > tables within the system... ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
