On 1/20/14 1:55 PM, Robert Haas wrote:
On Mon, Jan 20, 2014 at 7:16 AM, Marko Tiikkaja <ma...@joh.to> wrote:
What's so hard about plpgsql.warnings='all'? Or if the fact that it's a
list is your concern, I'm not going to oppose to making it a boolean.
Sure, that'd be fine. What I don't want is to have to start each function with:
#option warn_this
#option warn_that
#option warn_theotherthing
#option warn_somethingelse
#option warn_yetanotherthing
#option warn_whatdoesthisdoagain
Right. Completely agreed. The only reason I had them in the patch is
to have the ability to turn *off* a specific warning for a particular
function. But even that's of a bit dubious a value.
Also, I think that the way we've been doing it, each of those needs to
become a PL/pgsql keyword. That's going to become a problem at some
point.
Yeah, probably. :-(
Regards,
Marko Tiikkaja
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
