| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
| 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 14:20:18 |
| Message-ID: | 8d78fe3c-5ecf-4c66-b0e1-d36950c6ab9d@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.03.24 16:55, Jelte Fennema-Nio wrote:
> On Fri, 8 Mar 2024 at 15:51, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> What is the relationship of these changes with the recently added
>> backtrace_on_internal_error?
>
> I think that's a reasonable question. And the follow up ones too.
>
> I think it all depends on how close we consider
> backtrace_on_internal_error and backtrace_functions. While they
> obviously have similar functionality, I feel like
> backtrace_on_internal_error is probably a function that we'd want to
> turn on by default in the future. While backtrace_functions seems like
> it's mostly useful for developers. (i.e. the current grouping of
> backtrace_on_internal_error under DEVELOPER_OPTIONS seems wrong to me)
Hence the idea
backtrace_on_error = {all|internal|none}
which could default to 'internal'.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2024-03-13 14:28:54 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | Dean Rasheed | 2024-03-13 14:12:05 | Re: MERGE ... RETURNING |