Re: Support a wildcard in backtrace_functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Support a wildcard in backtrace_functions
Date
Msg-id 5629.1714156756@sss.pgh.pa.us
Whole thread Raw
In response to Re: Support a wildcard in backtrace_functions  (Andres Freund <andres@anarazel.de>)
Responses Re: Support a wildcard in backtrace_functions
Re: Support a wildcard in backtrace_functions
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I don't think enabling backtraces without a way to disable them is a good idea
> - security vulnerablilities in backtrace generation code are far from unheard
> of and can make error handling a lot slower...

Well, in that case we have to have some kind of control GUC, and
I think the consensus is that the one we have now is under-designed.
So I also vote for a full revert and try again in v18.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Support a wildcard in backtrace_functions
Next
From: Isaac Morland
Date:
Subject: Re: Why don't we support external input/output functions for the composite types