| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
| 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:04:07 |
| Message-ID: | 131F4E9A-AB82-4B04-BD02-F41A0E63B907@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 27 Feb 2024, at 18:03, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
>
> On Mon, 12 Feb 2024 at 14:27, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
>> Would a backtrace_functions_level GUC that would default to ERROR be
>> acceptable in this case?
>
> I implemented it this way in the attached patchset.
I'm not excited about adding even more GUCs but maybe it's the least bad option
here.
+ If a log entry is raised with a level higher than
+ <xref linkend="guc-backtrace-functions-min-level"/> and the name of the
This should be "equal to or higher" right?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-02-28 18:50:19 | Re: Support a wildcard in backtrace_functions |
| Previous Message | Joe Conway | 2024-02-28 17:43:24 | Re: An improved README experience for PostgreSQL |