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

From Robert Haas
Subject Re: Support a wildcard in backtrace_functions
Date
Msg-id CA+TgmoaghPR2QxuxHRnNjqrYYwuc0nf7NRboPbZz7N7SVO6oCg@mail.gmail.com
Whole thread Raw
In response to Re: Support a wildcard in backtrace_functions  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Support a wildcard in backtrace_functions
List pgsql-hackers
On Mon, Apr 22, 2024 at 2:36 AM Michael Paquier <michael@paquier.xyz> wrote:
> I'd like to think about this stuff in a different way: this is useful
> if enabled by default because it can also help in finding out error
> paths that should not use the internal errcode.  Normally, there
> should be zero backtraces produced, except in unexpected
> never-to-be-reached cases.

That's long been my feeling about this. So, if we revert this for now,
what we ought to do is put it back right ASAP after feature freeze and
then clean all that up.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Support event trigger for logoff
Next
From: Masahiko Sawada
Date:
Subject: Re: promotion related handling in pg_sync_replication_slots()