Backport injection_points: injection_points_attach overload with library, function, and private data (v18)#937
Merged
a-masterov merged 1 commit intoREL_18_STABLE_neonfrom Mar 30, 2026
Conversation
hlinnaka
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change backports postgres/postgres@16a2f70, which adds a second overload of
injection_points_attachthat takes an explicit library name, function name, and optional bytea private data, so tests can attach callbacks without hard-coding the injection_points module wrapper.Because that commit’s regression test lists attached points, it also adds
InjectionPointList()in the core and exposes it viainjection_points_list()in the injection_points test extension, matching upstream.The injection_points SQL regression test and expected output are extended accordingly.
Note: injection_points--1.0.sql is updated; existing databases that already have the extension may need a separate upgrade script if you rely on ALTER EXTENSION ... UPDATE rather than recreating the extension.