>> Maybe new constraint_exclusion staff could help to exclude non-matching
>> tables from inheritance query ?
> Yes, that's exactly what it's for. Your testing is welcome. Download 8.1
> and try it today.
Great, I'm developing on 8.1b2 now...
But could you be more particular about the solution ?
Only the way I can think of is to add "relname" field into parent table, add
"BEFORE INSERT" trigger to each child that will set it appropriately and
CHECK (relname=<here goes table name>).
It works in this case..
More than that.. I can create indexes on each table with "WHERE
relname!=<table name>", then they are used with DELETE/UPDATE WHERE relname
IN(..).
But the whole idea to adding an extra field, trigger and duplicating table
name multiple times.. Feels a bit stinky to me..
Could you suggest another path ?
