| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Call stacks and RAISE INFO |
| Date: | 2011-10-14 17:51:29 |
| Message-ID: | 1318614537-sup-8960@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Florian Pflug's message of vie oct 14 14:41:11 -0300 2011:
>
> On Oct14, 2011, at 19:27 , Josh Berkus wrote:
> >> I meant verbosity, not error level. This quick test shows what I meant
> >> -- but it doesn't work; the server log is altered as I expected (and does not
> >> include the context lines), but not plpgsql's:
> >
> > Yeah, what we'd need is a client_error_verbosity setting.
>
> We do transmit the individual parts of a NOTICE separately, so I'd say
> suppressing some of them is the client's job. So, instead of a GUC I'd say
> we'd need a psql setting ERROR_VERBOSITY.
Well, we do have a psql setting as well (\set VERBOSITY). But is Josh
using psql?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-10-14 18:00:30 | Re: Call stacks and RAISE INFO |
| Previous Message | Florian Pflug | 2011-10-14 17:41:11 | Re: Call stacks and RAISE INFO |