Re: Clobbered parameter names via DECLARE in PL/PgSQL
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Brendan Jurd <direvus@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-04-15T15:25:12Z
Lists: pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes: > We can raise warning from CREATE OR REPLACE FUNCTION - but I would to > like have plpgsql_check_function inside core - and it is better place > for this and similar issues. I agree. This is a perfectly legal use of nested declaration scopes, so it would be totally inappropriate to complain about it in normal use of a plpgsql function. On the other hand, it would probably be sane and useful for CHECK FUNCTION to flag any case where an inner declaration shadows an outer-scope name (not only the specific case of topmost block vs function parameter). regards, tom lane