Re: Support a wildcard in backtrace_functions

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support a wildcard in backtrace_functions
Date: 2025-02-18 12:29:27
Message-ID: 49358C71-DF9C-49EE-B768-C05CA469F9AD@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Feb 2025, at 09:34, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>
> On Thu, 27 Jun 2024 at 12:43, Jelte Fennema-Nio <me(at)jeltef(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-02-18 12:29:48 Re: Should heapam_estimate_rel_size consider fillfactor?
Previous Message Zhang Mingli 2025-02-18 12:11:22 Re: Fix outdated code comments in nodeAgg.c