On Mon, Jan 20, 2014 at 7:16 AM, Marko Tiikkaja <marko@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
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
