Re: pgsql: injection_points: Remove portions related to custom pgstats

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)lists(dot)postgresql(dot)org, Sami Imseih <samimseih(at)gmail(dot)com>
Subject: Re: pgsql: injection_points: Remove portions related to custom pgstats
Date: 2025-12-09 22:56:36
Message-ID: aTipJA1Y1zVSmH3H@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Dec 09, 2025 at 05:49:24PM -0500, Tom Lane wrote:
> They are updated when a new BF run is made for that branch, so
> back-patching the DROP EXTENSION commands should do the trick.

Okay, good to know. Let's do that then.

Encouraging a setup and a cleanup step seems like a good thing here,
as people like copy-pasting contents when creating a module. Should I
just go ahead and make that happen? The buildfarm breakage is still
on me based on the commit maths.

By the way, REGRESS in modules/nbtree/Makefile is missing
nbtree_half_dead_pages.. meson.build has both tests.
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2025-12-09 23:01:53 pgsql: Fix misleading comment in tuplesort.c
Previous Message Tom Lane 2025-12-09 22:49:24 Re: pgsql: injection_points: Remove portions related to custom pgstats