| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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-04-19 08:58:25 |
| Message-ID: | 84dc64fa-a35e-4cfa-860e-1adfd2dd58a2@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.04.24 11:54, Jelte Fennema-Nio wrote:
> On Thu, 18 Apr 2024 at 10:50, Peter Eisentraut<peter(at)eisentraut(dot)org> wrote:
>> Why exactly is this an open item? Is there anything wrong with the
>> existing feature?
> The name of the GUC backtrace_on_internal_error is so specific that
> it's impossible to extend our backtrace behaviour in future releases
> without adding yet another backtrace GUC. You started the discussion
> on renaming it upthread:
This presupposes that there is consensus about how the future
functionality should look like. This topic has gone through half a
dozen designs over a few months, and I think it would be premature to
randomly freeze that discussion now and backport that design.
If a better, more comprehensive design arises for PG18, I think it would
be pretty easy to either remove backtrace_on_internal_error or just
internally remap it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2024-04-19 09:00:00 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Previous Message | Bertrand Drouvot | 2024-04-19 08:56:25 | Re: Disallow changing slot's failover option in transaction block |