| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 21:55:20 |
| Message-ID: | 26487.1318629320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 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).
Oh? I don't see that. AFAICT the behavior is not dependent on the
error severity level. RAISE just automatically suppresses the context
line from the current plpgsql function. Not sure if we need to make
that part of the behavior configurable or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-14 21:59:52 | Re: WIP: collect frequency statistics for arrays |
| Previous Message | Tom Lane | 2011-10-14 21:51:07 | Re: Call stacks and RAISE INFO |