"Jim Buttafuoco" <[EMAIL PROTECTED]> writes: > The check constraints on table s are not like the original, I have an extra > t_a_check constraint. Is this correct?
I wouldn't say it's correct but it is known. I think the plan is to have such constraints be marked so you *can't* drop them as long as you're a child of another table that has them. But Postgres doesn't yet track where constraints came from or check that you don't drop ones that are inherited. -- greg ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
