| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Subject: | Re: Injection points: some tools to wait and wake |
| Date: | 2024-03-04 09:51:41 |
| Message-ID: | CAGECzQQ-rEPem3=s-esDo=tvLsq2Wt1-NrwroyUuZpYfby2nDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 4 Mar 2024 at 06:27, Michael Paquier <michael(at)paquier(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-03-04 09:51:52 | Re: Synchronizing slots from primary to standby |
| Previous Message | Hayato Kuroda (Fujitsu) | 2024-03-04 09:50:27 | RE: Some shared memory chunks are allocated even if related processes won't start |