| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: PL/pgSQL, RAISE and error context |
| Date: | 2015-04-24 17:47:48 |
| Message-ID: | CAFj8pRApD=nE2YbEoWgvc0jBYsokb6B7zjzkbPABQss2hF6WOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2015-04-24 19:16 GMT+02:00 Joel Jacobson <joel(at)trustly(dot)com>:
> On Fri, Apr 24, 2015 at 6:07 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-04-24 18:26:15 | Re: Moving ExecInsertIndexTuples and friends to new file |
| Previous Message | Joel Jacobson | 2015-04-24 17:16:04 | Re: PL/pgSQL, RAISE and error context |