Re: Call stacks and RAISE INFO - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: Call stacks and RAISE INFO
Date
Msg-id FFFBE1A3-21D9-433E-9E05-34CCACA97C11@phlo.org
Whole thread Raw
In response to Re: Call stacks and RAISE INFO  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Oct14, 2011, at 20:00 , Josh Berkus wrote:
>>> 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?

Yeah, I meant that we could split that into two settings, one for level >= ERROR
and one for level < ERROR. It'd certainly be nice to be able to report progress messages
from functions without seeing all the CONTEXT and STATEMENT noise when running them via
psql, yet still get that information if an actual error occurs.

> Not in this instance, no.

But I still believe this is something that should be done client-side.

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: DOMAINs and CASTs
Next
From: Florian Pflug
Date:
Subject: Re: Call stacks and RAISE INFO