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

From Daniel Gustafsson
Subject Re: Support a wildcard in backtrace_functions
Date
Msg-id 49358C71-DF9C-49EE-B768-C05CA469F9AD@yesql.se
Whole thread Raw
In response to Re: Support a wildcard in backtrace_functions  (Jelte Fennema-Nio <me@jeltef.nl>)
List pgsql-hackers
> On 18 Feb 2025, at 09:34, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> 
> On Thu, 27 Jun 2024 at 12:43, Jelte Fennema-Nio <me@jeltef.nl> wrote:
>> Attached is a rebased patchset of my previous proposal, including a
>> few changes that Michael preferred:
> 
> Rebased again. (got notified because of the new commitfest rebase emails)

We typically avoid having intra-depencies between multiple GUCs to control a
single behavior like this.  I'm not sure having three is the right move here
but I need to do some more review and testing.

> The first patch should be trivial to commit at least as it's just cleanup.

Agreed, I've applied that to keep it from getting lost in here.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Zhang Mingli
Date:
Subject: Re: Fix outdated code comments in nodeAgg.c
Next
From: Heikki Linnakangas
Date:
Subject: Re: Should heapam_estimate_rel_size consider fillfactor?