From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
---|---|
To: | 'Antonin Houska' <ah(at)cybertec(dot)at> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Move the injection_points extension to contrib? |
Date: | 2025-07-07 09:02:05 |
Message-ID: | OSCPR01MB14966D3BACFD1B2FEF230FD2BF54FA@OSCPR01MB14966.jpnprd01.prod.outlook.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Antonin,
> Having the extension in contrib would be useful in cases a 3rd party extension
> uses injection points in its regression tests. In particular, it's more
> practical for CI to install the "injection_points" extension by installing the
> "contrib" binary package than by building the whole server from source. (AFAIK
> the src/modules/injection_points directory is currently not included in any
> package.)
IIRC, one of the motivation why we put src/test/modules is to ensure the flexiblity.
Even contrib modules must follow the rule [1]. E.g., ABI must be kept and API
change should be considered carefully - commits like [2] may be restricted.
Also We may even have to consider that whether the name of injection points
should be kept or not.
How do you feel?
[1]: https://www.postgresql.org/docs/devel/xfunc-c.html#XFUNC-GUIDANCE-API-COMPATIBILITY
[2]: https://github.com/postgres/postgres/commit/f4af4515bb5f3591d49bc16b6cb8ddbf66f98374
Best regards,
Hayato Kuroda
FUJITSU LIMITED
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2025-07-07 09:07:43 | Re: Logical Replication of sequences |
Previous Message | Nazir Bilal Yavuz | 2025-07-07 08:45:06 | Re: meson vs. llvm bitcode files |