<p dir="ltr"><br /> Dne 26. 1. 2014 23:24 "Simon Riggs" <<a
href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>>napsal(a):<br /> ><br /> > On 26 January 2014
15:53,Pavel Stehule <<a href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>> wrote:<br /> >
><br/> > ><br /> > ><br /> > > 2014-01-26 Florian Pflug <<a
href="mailto:fgp@phlo.org">fgp@phlo.org</a>><br/> > ><br /> > >> On Jan26, 2014, at 10:19 , Simon
Riggs<simon@2ndQuadrant.com> wrote:<br /> > >> > Also, having<br /> > >> >
plpgsql.warnings_as_errors= off (default) | on<br /> > >> > makes sense and should be included in 9.4<br
/>> >><br /> > >> I still think this is a bad idea, for the same reasons I don't like<br /> >
>>consistent_into (discussed in a separate thread).<br /> > >><br /> > >> But these objections
wouldgo away if restricted this to function<br /> > >> creation time only. So even with warnings_as_errors=on,
you<br/> > >> could still *call* a function that produces a warning, but not<br /> > >> *create*
one.<br/> > ><br /> > ><br /> > > +1 behave - and please, better name<br /> ><br /> > +1 to
that.<br/> ><br /> > I guess I only saw that way of working because I was thinking of it as<br /> > a
"compilerwarning".<br /> ><br /> > So perhaps we should call it<br /> >
plpgsql.compiler_warnings_as_errors<br/> ><br /> > to make that behaviour more clear.<br /> ><br /> >
plpgsql.error_on_create_warnings<pdir="ltr">I have a problém with joining word error and warning together.<p
dir="ltr">Somelike stop_on_compilation_warning or strict_compiler sound me more logical <p dir="ltr">Regards<p
dir="ltr">Pavel<br/> ><br /> > --<br /> > Simon Riggs <a
href="http://www.2ndQuadrant.com/">http://www.2ndQuadrant.com/</a><br/> > PostgreSQL Development, 24x7 Support,
Training& Services<br />
