Error prone compilation of stored procedure

What's the reason behind very "tolerant" error checking during stored
procedure compilation?
Why PostgreSQL allows using variable (j_var) that doesn't exists? It isn't
column name or isn't declared anywhere. Like in example below:

CREATE OR REPLACE FUNCTION test()
RETURNS int AS
$BODY$
BEGIN

select 1 WHERE 1 > j_var;
RETURN 2;
END;
$BODY$
LANGUAGE plpgsql VOLATILE
COST 100;

--
View this message in context: http://postgresql.nabble.com/Error-prone-compilation-of-stored-procedure-tp5856699.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.