Re: plpgsql.warn_shadow

On Jan15, 2014, at 01:34 , Marko Tiikkaja <marko@joh.to> wrote:
> It's me again, trying to find a solution to the most common mistakes I make.  This time it's accidental shadowing of
variables,especially input variables.  I've wasted several hours banging my head against the wall while shouting "HOW
CANTHIS VARIABLE ALWAYS BE NULL?".  I can't believe I'm the only one.  To give you a rough idea on how it works: 

I like this, but think that the option should be just called plpgsql.warnings or plpgsql.warn_on and accept a list of
warningsto enable. I'm sure you'll come up with more unsafe coding practices to warn about in the future - for example,
consistent_intoimmediately comes to mind ;-) 

best regards,
Florian Pflug