If a column type is being changed with USING (NULL) clause,
NOT NULL constraint seems not to be checked:

fduch@~=# CREATE table test (x integer not null);
CREATE TABLE
fduch@~=# INSERT INTO test VALUES (1);
INSERT 0 1
fduch@~=# ALTER TABLE test ALTER x TYPE boolean USING (NULL);
ALTER TABLE
fduch@~=# \d test
Table "public.test"
Column | Type | Modifiers
--------+---------+-----------
x | boolean | not null

fduch@~=# SELECT * from test;
x
---

(1 row)

fduch@~=# SELECT version();
version
------------------------------------------------------------------------------------------------
PostgreSQL 8.1.4 on i386-portbld-freebsd6.1, compiled by GCC cc (GCC) 3.4.4 [FreeBSD] 20050518
(1 row)


8.0 branch has the same behavour.


--
Fduch M. Pravking

---------------------------(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

"Alexander M. Pravking" <fduch (AT) antar (DOT) bryansk.ru> writes:
Hm, the code seems to have provisions to check "SET NOT NULL", but
it fails to check pre-existing NOT NULL attributes :-(

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

"Alexander M. Pravking" <fduch (AT) antar (DOT) bryansk.ru> writes:
I've committed patches for this. Thanks for the report.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: 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