That's all I needed to know. Thanks. --- To answer some of the other comments: This was a simplified example to show the issue. In the actual case the table was much more complex with a lot of different CHECK constraints, and a default value for one them had a typo making it invalid. It took a while to figure out which CHECK was giving the error when you don't expect a presumably accepted default value during table creation to be the culprit. Perhaps, if the error message was a bit more informative by giving you which column is in CHECK violation, things would be easier. Thank you all.