Re: Support a wildcard in backtrace_functions

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-27 17:03:17
Message-ID: CAGECzQSxASJGLrD8h7-wR5d_H+JYCbH2ZHa4wtGbbg3WabB1rw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Attachment Content-Type Size
v3-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch text/x-patch 2.2 KB
v3-0001-Add-backtrace_functions_min_level.patch text/x-patch 5.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-02-27 17:29:17 Re: Fix for edge case in date_bin() function
Previous Message Alvaro Herrera 2024-02-27 16:26:07 Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock