| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Florian Pflug <fgp(at)phlo(dot)org>, Marti Raudsepp <marti(at)juffo(dot)org> |
| Subject: | Re: plpgsql.warn_shadow |
| Date: | 2014-02-03 20:48:31 |
| Message-ID: | 52F0009F.9060205@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-03 9:17 PM, Pavel Stehule wrote:
> I am not happy from "warnings_as_error"
>
> what about "stop_on_warning" instead?
abort_compilation_on_warning? I think if we're not going to make it
more clear that warnings are only promoted to errors at CREATE FUNCTION
time, we can't do much better than warnings_as_errors.
> 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.
Is this really an issue considering these errors can only happen when
someone runs CREATE FUNCTION?
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2014-02-03 20:50:09 | Re: postgres FDW cost estimation options unrecognized in 9.3-beta1 |
| Previous Message | Pavel Stehule | 2014-02-03 20:17:31 | Re: plpgsql.warn_shadow |