Re: plpgsql.warn_shadow - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: plpgsql.warn_shadow
Date
Msg-id 5322E1C8.4080100@joh.to
Whole thread Raw
In response to Re: plpgsql.warn_shadow  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: plpgsql.warn_shadow
List pgsql-hackers
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'
>    plpgsql.compile_errors = 'list'        default = 'none'
>
> Only possible values in 9.4 are 'shadow', 'all', 'none'

I'm fine with this.  I'm starting to think that runtime warnings are a 
bad idea anyway.


Regards,
Marko Tiikkaja



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Archive recovery won't be completed on some situation.
Next
From: Peter Geoghegan
Date:
Subject: Re: Failure while inserting parent tuple to B-tree is not fun