| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql.warn_shadow |
| Date: | 2014-01-27 10:40:29 |
| Message-ID: | CABRT9RD7tOgUsP=kHEAKY3Sa+KB-G4bK_8a5DMEj_fkoNeLxkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 26, 2014 at 11:19 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> For 9.4, we should cut down the patch so it has
> plpgsql.warnings = none (default) | all | [individual item list]
> plpgsql.warnings_as_errors = off (default) | on
I hope I'm not late for the bikeshedding :)
Why not have 2 similar options:
plpgsql.warnings = none (default) | all | [individual item list]
plpgsql.errors = none (default) | all | [individual item list]
That would be cleaner, more flexible, and one less option to
set if you just want errors and no warnings.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-01-27 10:54:13 | Re: plpgsql.warn_shadow |
| Previous Message | Alexander Korotkov | 2014-01-27 10:32:29 | Re: GIN improvements part2: fast scan |