| 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-22 10:09:34 |
| Message-ID: | CAGECzQQTF19QdmNR1tCT-r4OjNa3EA=ygpAucae5-rUTbqqwQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 21 Mar 2024 at 15:41, Jelte Fennema-Nio <me(at)jeltef(dot)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.
| Attachment | Content-Type | Size |
|---|---|---|
| v9-0002-Restructure-backtrace-related-GUCs.patch | application/octet-stream | 15.6 KB |
| v9-0001-Add-PGErrorVerbosity-to-typedefs.list.patch | application/octet-stream | 1.3 KB |
| v9-0003-Change-log_backtrace-default-to-internal.patch | application/octet-stream | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-03-22 10:14:13 | Re: Support a wildcard in backtrace_functions |
| Previous Message | Maxim Orlov | 2024-03-22 09:58:28 | Re: Bug in nbtree optimization to skip > operator comparisons (or < comparisons in backwards scans) |