The following bug has been logged online:

Bug reference: 1293
Logged by: Alexander Kirpa

Email address: postgres (AT) bilteks (DOT) com

PostgreSQL version: 8.0 Beta

Operating system: FreeBSD

Description: INSERT INTO test (f1.f2) VALUES (1,2) - wrong diagnostic

Details:

create table test(f1 int4,f2 int4);
insert into test (f1.f2) values (1,2);
ERROR: cannot assign to a column of type integer because it is not a
composite type
select f1.f2 from test;
relation "f1" does not exist

Wrong diagnostic for INSERT


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

"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
This diagnostic is not wrong. It might be a tad unhelpful, but I don't
think it's within the province of the parser to intuit that you meant to
type a comma instead of a period.

regards, tom lane

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