The following bug has been logged online:

Bug reference: 1433
Logged by: craig perras
Email address: craigp98072 (AT) yahoo (DOT) com
PostgreSQL version: 8.0 release
Operating system: win2000
Description: domain check constraint not checked when adding new
column
Details:

Domain check constraint not checked when adding new column.

repro:
add domain 'string' of base type text with non-null constraint
add column of type 'string' to table with existing rows
works; all rows have new column's value set to null

expected:
error: cannot add column due to non-null constraint in domain 'string'

notes:
could not insert a new row with non-null value for 'string' column (as
expected)
trying to add a column of type text with non-null constraint produces
expected error message

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

"craig perras" <craigp98072 (AT) yahoo (DOT) com> writes:
Hmm. It does work for cases like

regression=# create domain posint int check (value > 0);
CREATE DOMAIN
regression=# alter table foo add column f5 posint default 0;
ERROR: value for domain posint violates check constraint "posint_check"

I think the issue is that when you don't specify any default, the scan
of the table gets optimized away.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

"craig perras" <craigp98072 (AT) yahoo (DOT) com> writes:
Fixed for 8.0.1.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org