Re: Support a wildcard in backtrace_functions

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: Support a wildcard in backtrace_functions
Date: 2024-02-12 15:27:45
Message-ID: 6b633f3b-aee1-41ba-922b-6acb8e7c3be0@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12.02.24 14:27, Jelte Fennema-Nio wrote:
> And honestly wanting
> to get backtraces for non-ERROR log entries seems quite niche to me,
> which to me makes it a weird default.

I think one reason for this is that non-ERRORs are fairly unique in
their wording, so you don't have to isolate them by function name.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-02-12 15:49:45 Re: [PATCH] allow pg_current_logfile() execution under pg_monitor role
Previous Message Peter Eisentraut 2024-02-12 15:18:12 Re: table inheritance versus column compression and storage settings