| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Call stacks and RAISE INFO |
| Date: | 2011-10-14 18:00:30 |
| Message-ID: | 4E9878BE.5050902@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 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?
Not in this instance, no.
In any case, this doesn't address the inconsistency of supressing
CONTEXT for the first level of the call stack with RAISE INFO but not
for the others. (RAISE EXCEPTION shows CONTEXT for all levels of the
call stack).
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-14 18:16:40 | Re: patch: move dumpUserConfig call in dumpRoles function of pg_dumpall.c |
| Previous Message | Alvaro Herrera | 2011-10-14 17:51:29 | Re: Call stacks and RAISE INFO |