Re: Support a wildcard in backtrace_functions
От | Jelte Fennema-Nio |
---|---|
Тема | Re: Support a wildcard in backtrace_functions |
Дата | |
Msg-id | CAGECzQTChkvn5Xj772LB3=xo2x_LcaO5O0HQvXqobm1xVp6+4w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Support a wildcard in backtrace_functions (Jelte Fennema-Nio <me@jeltef.nl>) |
Ответы |
Re: Support a wildcard in backtrace_functions
|
Список | pgsql-hackers |
On Fri, 22 Mar 2024 at 11:09, Jelte Fennema-Nio <me@jeltef.nl> wrote: > On Thu, 21 Mar 2024 at 15:41, Jelte Fennema-Nio <me@jeltef.nl> wrote: > > Attached is a patch that implements this. Since the more I think about > > it, the more I like this approach. > > I now added a 3rd patch to this patchset which changes the > log_backtrace default to "internal", because it seems quite useful to > me if user error reports of internal errors included a backtrace. I think patch 0002 should be considered an Open Item for PG17. Since it's proposing changing the name of the newly introduced backtrace_on_internal_error GUC. If we want to change it in this way, we should do it before the release and preferably before the beta. I added it to the Open Items list[1] so we don't forget to at least decide on this. [1]: https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items
В списке pgsql-hackers по дате отправления: