Re: Support a wildcard in backtrace_functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support a wildcard in backtrace_functions
Date
Msg-id 6b633f3b-aee1-41ba-922b-6acb8e7c3be0@eisentraut.org
Whole thread Raw
In response to Re: Support a wildcard in backtrace_functions  (Jelte Fennema-Nio <me@jeltef.nl>)
List 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.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: table inheritance versus column compression and storage settings
Next
From: Nathan Bossart
Date:
Subject: Re: [PATCH] allow pg_current_logfile() execution under pg_monitor role