Re: Persist injection points across server restarts

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Jeff Davis <pgsql@j-davis.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, "Maksim.Melnikov" <m.melnikov@postgrespro.ru>
Date: 2025-06-04T00:15:08Z
Lists: pgsql-hackers
On Tue, Jun 03, 2025 at 03:34:16PM -0400, Andres Freund wrote:
> I'm somewhat doubtful this is is the right direction. Tests that require
> injection points before consistency also can't wait for injection points using
> the SQL interface or such, so most of the stuff has to be written in C
> anyway. And if so, you also can attach to injection points in the relevant
> shared_preload_libraries entry.

Hmm.  I'm wondering about an alternate approach here: a postmaster GUC
in injection_points that can take in input a list of
name/library/function where the module would load them when
initializing.  That's a bit artistic, perhaps, still it would work
without having to worry about the flush and reload steps.
--
Michael

Commits

  1. Add InjectionPointList() to retrieve list of injection points