digoal
2024-04-09
PostgreSQL , PolarDB , DuckDB , injection_points
《PostgreSQL 17 preview - 新增代码注入功能(enable-injection-points), 类似hook.》
injection_points: Introduce runtime conditions
author Michael Paquier <michael@paquier.xyz>
Mon, 8 Apr 2024 00:47:50 +0000 (09:47 +0900)
committer Michael Paquier <michael@paquier.xyz>
Mon, 8 Apr 2024 00:47:50 +0000 (09:47 +0900)
commit f587338dec87d3c35b025e131c5977930ac69077
tree 1e22b2e03cf17a034da5e62ed4173ec4e6f347a4 tree
parent 705843d294d5d3bc5cce4001596df4df5f1c8b59 commit | diff
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/ZfP7IDs9TvrKe49x@paquier.xyz
