On 3 February 2014 20:17, Pavel Stehule <pavel.steh...@gmail.com> wrote: > Hello > > I am not happy from "warnings_as_error" > > what about "stop_on_warning" instead? > > second question: should be these errors catchable or uncatchable? > > When I work on large project, where I had to use some error handler of > "EXCEPTION WHEN OTHERS" I found very strange and not useful so all syntax > errors was catched by this handler. Any debugging was terribly difficult and > I had to write plpgsql_lint as solution.
The patch looks fine, apart from some non-guideline code formatting issues. Having looked at gcc and clang, I have a proposal for naming/API We just have two variables plpgsql.compile_warnings = 'list' default = 'none' plpgsql.compile_errors = 'list' default = 'none' Only possible values in 9.4 are 'shadow', 'all', 'none' If we can agree something quickly then we can commit this for 9.4 -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
