| 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-04-10 09:07:00 |
| Message-ID: | CAGECzQTChkvn5Xj772LB3=xo2x_LcaO5O0HQvXqobm1xVp6+4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 22 Mar 2024 at 11:09, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-04-10 09:15:37 | Re: Speed up clean meson builds by ~25% |
| Previous Message | Alexander Lakhin | 2024-04-10 09:00:00 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |