> No, and TBH I would vote strongly against including that much detail in > this error message anyway. That info could be indefinitely long, and it's > not especially relevant to the stated error condition --- for example, the > presence of a default is *not* relevant to whether the column matches the > parent. I'm okay with shoehorning column type into this message, but not > much more than that. > > regards, tom lane >
Ok, that makes sense. How about things like NOT NULL? you get an error if your column doesn't have that.