From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Call stacks and RAISE INFO |
Date: | 2011-10-14 17:14:38 |
Message-ID: | 1318612401-sup-6503@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Josh Berkus's message of vie oct 14 13:52:32 -0300 2011:
> 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?
Maybe set the verbosity to a lower level in the function? I dunno if
plpgsql lets you do that though. We have a GUC that controls the server
log verbosity, and psql can do it too; but plpgsql is sort of in
between.
--
Á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 17:16:43 | Re: Call stacks and RAISE INFO |
Previous Message | Josh Berkus | 2011-10-14 17:14:27 | Re: Bugs in information_schema.referential_constraints view |