Taiki Yamaguchi <[EMAIL PROTECTED]> writes:
> I found a small error in "5.8 Inheritance" where it says:
> Check constraints can be defined on tables within an inheritance
> hierarchy. All check constraints on a parent table are automatically
> inherited by all of its children. Other types of constraints are not
> inherited, however.
> However, "not null" constraints also will be inherited. Unique
> constraints, primary key and foreign keys are not.
I think whoever wrote that had in mind that not-null constraints are a
special case of check constraints. I agree it's clearer to spell it out
though. Done, thanks for the report.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
