Re: bugfix: incomplete implementation of errhidecontext - Mailing list pgsql-hackers

From Andres Freund
Subject Re: bugfix: incomplete implementation of errhidecontext
Date
Msg-id 20150707121305.GN30359@alap3.anarazel.de
Whole thread Raw
In response to Re: bugfix: incomplete implementation of errhidecontext  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: bugfix: incomplete implementation of errhidecontext  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: patch : Allow toast tables to be moved to a different tablespace
Next
From: Andres Freund
Date:
Subject: Re: Tab completion for CREATE SEQUENCE