Re: plpgsql.warn_shadow

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql.warn_shadow
Date: 2014-01-27 10:54:13
Message-ID: CAFj8pRB0WX2hUSqXGCXmFmNzFF-Joc3oichGq0Kmaj7GLo6AKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2014-01-27 Marti Raudsepp <marti(at)juffo(dot)org>

> On Sun, Jan 26, 2014 at 11:19 AM, Simon Riggs <simon(at)2ndquadrant(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2014-01-27 11:04:49 Re: plpgsql.warn_shadow
Previous Message Marti Raudsepp 2014-01-27 10:40:29 Re: plpgsql.warn_shadow