Re: plpgsql.warn_shadow - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: plpgsql.warn_shadow
Date
Msg-id CAFj8pRB0WX2hUSqXGCXmFmNzFF-Joc3oichGq0Kmaj7GLo6AKw@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql.warn_shadow  (Marti Raudsepp <marti@juffo.org>)
List pgsql-hackers



2014-01-27 Marti Raudsepp <marti@juffo.org>
On Sun, Jan 26, 2014 at 11:19 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> For 9.4, we should cut down the patch so it has
>   plpgsql.warnings = none (default) | all | [individual item list]

>   plpgsql.warnings_as_errors = off (default) | on

I hope I'm not late for the bikeshedding :)

Why not have 2 similar options:
plpgsql.warnings = none (default) | all | [individual item list]
plpgsql.errors = none (default) | all | [individual item list]

That would be cleaner, more flexible, and one less option to
set if you just want errors and no warnings.

what means plpgsql.errors = none ???

I strongly disagree so this design is clean

Regards

Pavel
 

Regards,
Marti


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: plpgsql.warn_shadow
Next
From: Simon Riggs
Date:
Subject: Re: plpgsql.warn_shadow