| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, 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-03-14 12:12:18 |
| Message-ID: | CA+U5nMKY8Sfe++KRA45_zR5q71SN=dnxDX_WGqjCoHXWgkJEpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14 March 2014 11:10, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
>
> 2014-03-14 12:02 GMT+01:00 Marko Tiikkaja <marko(at)joh(dot)to>:
>
>> On 3/14/14 10:56 AM, Simon Riggs wrote:
>>>
>>> The patch looks fine, apart from some non-guideline code formatting
>>> issues.
>>
>>
>> I'm not sure what you're referring to. I thought it looked fine.
>>
>>
>>> Having looked at gcc and clang, I have a proposal for naming/API
>>>
>>> We just have two variables
>>>
>>> plpgsql.compile_warnings = 'list' default = 'none'
>
>
> +1
>
>>>
>>> plpgsql.compile_errors = 'list' default = 'none'
>>>
>>> Only possible values in 9.4 are 'shadow', 'all', 'none'
>
>
> what is compile_errors ? We don't allow to ignore any error now.
How about
plpgsql.additional_warnings = 'list'
plpgsql.additional_errors = 'list'
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2014-03-14 12:12:39 | Re: Archive recovery won't be completed on some situation. |
| Previous Message | Oleg Bartunov | 2014-03-14 11:52:37 | Re: jsonb and nested hstore |