| From: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Support a wildcard in backtrace_functions |
| Date: | 2024-02-28 18:50:19 |
| Message-ID: | CAGECzQS=L1-Lszs_VfQxpYSfHwyv3eXEjxu6_7cajmnmbYjkCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 28 Feb 2024 at 19:04, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> This should be "equal to or higher" right?
Correct, nicely spotted. Fixed that. I also updated the docs for the
new backtrace_functions_min_level GUC itself too, as well as creating
a dedicated options array for the GUC. Because when updating its docs
I realized that none of the existing level arrays matched what we
wanted.
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch | text/x-patch | 2.2 KB |
| v4-0001-Add-backtrace_functions_min_level.patch | text/x-patch | 6.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-02-28 18:51:02 | Re: An improved README experience for PostgreSQL |
| Previous Message | Daniel Gustafsson | 2024-02-28 18:04:07 | Re: Support a wildcard in backtrace_functions |