Ashutosh Bapat <ashutosh.ba...@enterprisedb.com> writes: > The way this patch has been written, it doesn't allow creating tables > with unknown type columns, which was allowed earlier.
Yes, that's an intentional change; creating such tables (or views) has never been anything but a foot-gun. However, I thought the idea was to silently coerce affected columns from unknown to text. This doesn't look like the behavior we want: > You might want to add some testcases to test the error report e.g. > (not necessarily in the same form) create view sv as select > relname::unknown from pg_class; > ERROR: column "relname" has type "unknown" regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers