Re: plpgsql.warn_shadow
От | Pavel Stehule |
---|---|
Тема | Re: plpgsql.warn_shadow |
Дата | |
Msg-id | CAFj8pRC9d15v0FMbCVF-+vY1XbqGxNKaJCnVoX9_6CQG-aNYdw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: plpgsql.warn_shadow (Marko Tiikkaja <marko@joh.to>) |
Ответы |
Re: plpgsql.warn_shadow
|
Список | pgsql-hackers |
2014-03-14 12:02 GMT+01:00 Marko Tiikkaja <marko@joh.to>:
+1
On 3/14/14 10:56 AM, Simon Riggs wrote:I'm not sure what you're referring to. I thought it looked fine.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'
+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.
I'm fine with this. I'm starting to think that runtime warnings are a bad idea anyway.
+1
Pavel
Regards,
Marko Tiikkaja
В списке pgsql-hackers по дате отправления: