aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/explain.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2025-05-10 06:56:26 +0900
committerMichael Paquier <michael@paquier.xyz>2025-05-10 06:56:26 +0900
commit371f2db8b05e4d46cbf489f05cbfc4d6ed6976d4 (patch)
treeaf10abf135f4a14534d31c7d8f95d7bed9b4e949 /src/backend/commands/explain.c
parent89372d0aaa4a6f0e560acdf9014c5ad66fdde1b1 (diff)
downloadpostgresql-371f2db8b05e4d46cbf489f05cbfc4d6ed6976d4.tar.gz
postgresql-371f2db8b05e4d46cbf489f05cbfc4d6ed6976d4.zip
Add support for runtime arguments in injection points
The macros INJECTION_POINT() and INJECTION_POINT_CACHED() are extended with an optional argument that can be passed down to the callback attached when an injection point is run, giving to callbacks the possibility to manipulate a stack state given by the caller. The existing callbacks in modules injection_points and test_aio have their declarations adjusted based on that. da7226993fd4 (core AIO infrastructure) and 93bc3d75d8e1 (test_aio) and been relying on a set of workarounds where a static variable called pgaio_inj_cur_handle is used as runtime argument in the injection point callbacks used by the AIO tests, in combination with a TRY/CATCH block to reset the argument value. The infrastructure introduced in this commit will be reused for the AIO tests, simplifying them. Reviewed-by: Greg Burd <greg@burd.me> Discussion: https://postgr.es/m/Z_y9TtnXubvYAApS@paquier.xyz
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions