2015-07-07 14:13 GMT+02:00 Andres Freund <and...@anarazel.de>: > On 2015-07-03 06:20:14 +0200, Pavel Stehule wrote: > > I would to use it for controlling (enabling, disabling) CONTEXT in RAISE > > statement in plpgsql. I am thinking so one option for this purpose is > > enough, and I would not to add other option to specify LOG, CLIENT. > > I don't think a plpgsql function should be able to suppress all > context. From a security/debuggability POV that's a bad idea. The > context messages are the only way right now to have any chance of > tracing back what caused an error in a function because log_statements et > al. will not show it. >
It does it now. The context is not raised for exception raised by RAISE statement from PL/pgSQL - and I would to fix it. But sometimes the context is useless - for NOTICE level for example. I seen a strange workarounds - RAISE NOTIFY followed by PERFORM 10/0 to get a context from PLpgSQL call. Pavel
