From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Marti Raudsepp <marti(at)juffo(dot)org> |
Subject: | Re: plpgsql.warn_shadow |
Date: | 2014-02-03 01:59:35 |
Message-ID: | 52EEF807.8060206@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi everyone,
Here's a new version of the patch. Added new tests and docs and changed
the GUCs per discussion.
plpgsql.warnings_as_errors only affects compilation at CREATE FUNCTION time:
=# set plpgsql.warnings to 'all';
SET
=#* set plpgsql.warnings_as_errors to true;
SET
=#* select foof(1); -- compiled since it's the first call in this session
WARNING: variable "f1" shadows a previously defined variable
LINE 2: declare f1 int;
^
foof
------
(1 row)
=#* create or replace function foof(f1 int) returns void as
$$
declare f1 int;
begin
end $$ language plpgsql;
ERROR: variable "f1" shadows a previously defined variable
LINE 3: declare f1 int;
Currently, plpgsql_warnings is a boolean since there's only one warning
we implement. The idea is to make it a bit field of some kind in the
future when we add more warnings. Starting that work for 9.4 seemed
like overkill, though. I tried to keep things simple.
Regards,
Marko Tiikkaja
Attachment | Content-Type | Size |
---|---|---|
shadow_v2.patch | text/plain | 10.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2014-02-03 02:50:36 | Re: WITH ORDINALITY planner improvements |
Previous Message | Craig Ringer | 2014-02-03 01:54:32 | Re: bugfix patch for json_array_elements |