injection_points: Introduce runtime conditions
authorMichael Paquier <[email protected]>
Mon, 8 Apr 2024 00:47:50 +0000 (09:47 +0900)
committerMichael Paquier <[email protected]>
Mon, 8 Apr 2024 00:47:50 +0000 (09:47 +0900)
commitf587338dec87d3c35b025e131c5977930ac69077
tree1e22b2e03cf17a034da5e62ed4173ec4e6f347a4
parent705843d294d5d3bc5cce4001596df4df5f1c8b59
injection_points: Introduce runtime conditions

This adds a new SQL function injection_points_set_local() that can be
used to force injection points to be run only in the process where they
are attached.  This is handy for SQL tests to:
- Detach automatically injection points when the process exits.
- Allow tests with injection points to run concurrently with other test
suites, so as such modules do not have to be marked with
NO_INSTALLCHECK.

Currently, the only condition that can be registered is for a PID.
This could be extended to more kinds later, if required, like database
names/OIDs, roles, or more concepts I did not consider.

Using a single function for SQL scripts is an idea from Heikki
Linnakangas.

Reviewed-by: Andrey Borodin
Discussion: https://postgr.es/m/[email protected]
src/test/modules/injection_points/expected/injection_points.out
src/test/modules/injection_points/injection_points--1.0.sql
src/test/modules/injection_points/injection_points.c
src/test/modules/injection_points/sql/injection_points.sql
src/tools/pgindent/typedefs.list