Re: Fwd: Before triggers and usage in partitioned tables

Sergio Ramazzina <sramazzina(at)gmail(dot)com> writes:
> [ test case ]

It seems to work as expected for me:

regression=# insert into tpm_wind_dcn values ('r','i','2010-01-09',42);
INSERT 0 0
regression=# select * from tpm_wind_dcn;
router | interface | data | qora | m1 | m2 | m3 | m4 | m5 | m6
--------+-----------+------------+------+----+----+----+----+----+----
r | i | 2010-01-09 | 42 | | | | | |
(1 row)

regression=# select * from only tpm_wind_dcn;
router | interface | data | qora | m1 | m2 | m3 | m4 | m5 | m6
--------+-----------+------+------+----+----+----+----+----+----
(0 rows)

regression=# select * from tp_wind_dcn_day9;
router | interface | data | qora | m1 | m2 | m3 | m4 | m5 | m6
--------+-----------+------------+------+----+----+----+----+----+----
r | i | 2010-01-09 | 42 | | | | | |
(1 row)

I wonder whether you are confused about how inheritance works. Rows
that are in child tables are supposed to show up when the parent is
read (as in my first SELECT above), except when you specify ONLY
(as in my second SELECT).

regards, tom lane