| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Call stacks and RAISE INFO |
| Date: | 2011-10-14 16:52:32 |
| Message-ID: | 4E9868D0.9080800@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
All,
I'm noticing some inconsistent and (I believe) undesirable behavior on
RAISE INFO.
If you call a function, and it posts progress reports using RAISE INFO,
then you get the INFO statements plain back to the client. However, if
that function calls another function, then you also get a three-line
CONTEXT message ... and if the functions are recursively called, the
CONTEXT message will emit 3 lines for every level of the call stack.
This seems like reasonable behavior for RAISE EXCEPTION but not RAISE
INFO. It pretty much makes INFO notices useless as end-user feedback if
you have functions calling other functions because of the amount of
garbage on the screen. Is this a bug?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-10-14 16:59:54 | Re: tuning autovacuum |
| Previous Message | Bruce Momjian | 2011-10-14 16:52:31 | Re: SLRU limits |