Re: Persist injection points across server restarts

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Maksim(dot)Melnikov" <m(dot)melnikov(at)postgrespro(dot)ru>
Subject: Re: Persist injection points across server restarts
Date: 2025-06-04 00:15:08
Message-ID: aD-QDOegY0yrw1AW@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-06-04 01:10:44 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Previous Message Fujii Masao 2025-06-03 23:15:56 Re: Add log_autovacuum_{vacuum|analyze}_min_duration