Re: plpgsql.warn_shadow - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: plpgsql.warn_shadow
Date
Msg-id CABRT9RD7tOgUsP=kHEAKY3Sa+KB-G4bK_8a5DMEj_fkoNeLxkw@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql.warn_shadow  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: plpgsql.warn_shadow
Re: plpgsql.warn_shadow
List pgsql-hackers
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.

Regards,
Marti



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: GIN improvements part2: fast scan
Next
From: Pavel Stehule
Date:
Subject: Re: plpgsql.warn_shadow