Unintuitive behavior regarding inheritance

Hi all;

I started trying to use table partitioning to handle a rather odd case
in the software I am working on. I ran into an issue (one I can
correct in my code) that strikes me as extremely unintuitive. I
figured I would report it here as behavior I would like to see change.

The basic problem is that while nearly all table contraints are
inherited, unique constraints are not. This means that primary keys
and so forth end up having to be redefined on all child tables
explicitly as part of the table creation process. This is
sufficiently unintuitive that as a result I am having to go back and
amend contributions of people far more knowledgeable on this than I
am.

It would be really helpful in the future if unique constraints and
primary keys were inherited.

At least I can adjust code, but this is a pretty big gotcha which
could go unnoticed until you have duplicates for primary key fields in
specific child tables.

Best wishes,
Chris Travers