Re: Injection points: some tools to wait and wake - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Injection points: some tools to wait and wake
Date
Msg-id CAGECzQQ-rEPem3=s-esDo=tvLsq2Wt1-NrwroyUuZpYfby2nDg@mail.gmail.com
Whole thread Raw
In response to Re: Injection points: some tools to wait and wake  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Injection points: some tools to wait and wake
List pgsql-hackers
On Mon, 4 Mar 2024 at 06:27, Michael Paquier <michael@paquier.xyz> wrote:
> I have mentioned that on a separate thread,

Yeah, I didn't read all emails related to this feature

> Perhaps we could consider that as an exception in "contrib", or have a
> separate path for test modules we're OK to install (the calls had
> better be superuser-only if we do that).

Yeah, it makes sense that you'd want to backport fixes/changes to
this. As long as you put a disclaimer in the docs that you can do that
for this module, I think it would be fine. Our tests fairly regularly
break anyway when changing minor versions of postgres in our CI, e.g.
due to improvements in the output of isolationtester. So if changes to
this module require some changes that's fine by me. Seems much nicer
than having to copy-paste the code.



pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Some shared memory chunks are allocated even if related processes won't start
Next
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby