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

From Tom Lane
Subject Re: Call stacks and RAISE INFO
Date
Msg-id 26409.1318629067@sss.pgh.pa.us
Whole thread Raw
In response to Re: Call stacks and RAISE INFO  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Call stacks and RAISE INFO  (Josh Berkus <josh@agliodbs.com>)
Re: Call stacks and RAISE INFO  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
>> I meant verbosity, not error level.  This quick test shows what I meant
>> -- but it doesn't work; the server log is altered as I expected (and does not
>> include the context lines), but not plpgsql's:

> Yeah, what we'd need is a client_error_verbosity setting.

It seems to me that a client-side facility would be unlikely to do the
right things, because it has not got enough information to know which
messages came from plpgsql RAISE commands.  Moreover, it's not apparent
that a one-size-fits-all approach is suitable anyhow: it may be that
some RAISEs don't need context traceback while others could use it.

Now that we have syntax for adding miscellaneous options to RAISE
statements, what I suggest we consider is a RAISE option that suppresses
all context lines for the message, perhaps

RAISE NOTICE 'fee, fi, fo, fum' USING context = false;
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Underspecified window queries in regression tests
Next
From: Tom Lane
Date:
Subject: Re: Call stacks and RAISE INFO