Re: PL/pgSQL, RAISE and error context - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: PL/pgSQL, RAISE and error context
Date
Msg-id CAFj8pRApD=nE2YbEoWgvc0jBYsokb6B7zjzkbPABQss2hF6WOQ@mail.gmail.com
Whole thread Raw
In response to Re: PL/pgSQL, RAISE and error context  (Joel Jacobson <joel@trustly.com>)
List pgsql-hackers


2015-04-24 19:16 GMT+02:00 Joel Jacobson <joel@trustly.com>:
On Fri, Apr 24, 2015 at 6:07 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> Example:
>>
>> context_messages = -warning, -error, +notice
>
>
> I prefer your first proposal - and there is a precedent for plpgsql -
> plpgsql_extra_checks
>
> It is clean for anybody. +-identifiers looks like horrible httpd config. :)

I have to agree on that :) Just thought this is the best we can do if
we want to reduce the number of GUCs to a minimum.

It looks like discussion KDE x GNOME.

GUC that has simply effect on behave without performance impact should not be problem - like log_lock_wait, log_min_duration and similar. I am sure so we would it.

The problematic GUC are a performance, planner, bgwriter, checkpoint related. 

pgsql-hackers by date:

Previous
From: Joel Jacobson
Date:
Subject: Re: PL/pgSQL, RAISE and error context
Next
From: Peter Geoghegan
Date:
Subject: Re: Moving ExecInsertIndexTuples and friends to new file