Re: plpgsql.warn_shadow

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: plpgsql.warn_shadow
Дата
Msg-id CAFj8pRDxpZPY_=UZV=d-XXGxyQuoHeqa4yNdVKnRGEh0r3A6vg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: plpgsql.warn_shadow  (Simon Riggs <simon@2ndQuadrant.com>)
Список pgsql-hackers



2014-03-14 13:12 GMT+01:00 Simon Riggs <simon@2ndquadrant.com>:
On 14 March 2014 11:10, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
>
>
> 2014-03-14 12:02 GMT+01:00 Marko Tiikkaja <marko@joh.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'

I understand .

+1

Pavel
 

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: Archive recovery won't be completed on some situation.
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Add CREATE support to event triggers