From: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Support a wildcard in backtrace_functions |
Date: | 2024-03-13 15:32:28 |
Message-ID: | CAGECzQTooa00GyibgyL=sJjbpsj+o9PDM+1EVcj9P45rcCd_zQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 13 Mar 2024 at 15:20, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> Hence the idea
>
> backtrace_on_error = {all|internal|none}
>
> which could default to 'internal'.
I think one use-case that I'd personally at least would like to see
covered is being able to get backtraces on all warnings. How would
that be done with this setting?
backtrace_on_error = all
backtrace_min_level = warning
In that case backtrace_on_error seems like a weird name, since it can
include backtraces for warnings if you change backtrace_min_level. How
about the following aproach. It still uses 3 GUCs, but they now all
work together. There's one entry point and two additional filters
(level and function name)
# Says what log entries to log backtraces for
log_backtrace = {all|internal|none} (default: internal)
# Excludes log entries from log_include_backtrace by level
backtrace_min_level = {debug4|...|fatal} (default: error)
# Excludes log entries from log_include_backtrace if function name
# does not match list, but empty string disables this filter (thus
# logging for all functions)
backtrace_functions = {...} (default: '')
PS. Other naming option for log_backtrace could be log_include_backtrace
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2024-03-13 15:39:04 | Re: BitmapHeapScan streaming read user and prelim refactoring |
Previous Message | Bharath Rupireddy | 2024-03-13 15:14:50 | Re: Support a wildcard in backtrace_functions |