Re: Injection points: preloading and runtime arguments
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-07-16T04:09:21Z
Lists: pgsql-hackers
Attachments
- 0001-Add-INJECTION_POINT_CACHED.patch (text/x-diff) patch 0001
On Wed, Jul 10, 2024 at 01:16:15PM +0900, Michael Paquier wrote: > You mean with something that does a injection_point_cache_get() > followed by a callback run if anything is found in the local cache? > Why not. Based on what you have posted at [1], it looks like this had > better check the contents of the cache's generation with what's in > shmem, as well as destroying InjectionPointCache if there is nothing > else, so there's a possible dependency here depending on how much > maintenance this should do with the cache to keep it consistent. Now that 86db52a5062a is in the tree, this could be done with a shortcut in InjectionPointCacheRefresh(). What do you think about something like the attached, with your suggested naming? -- Michael
Commits
-
Add INJECTION_POINT_CACHED() to run injection points directly from cache
- a0a5869a8598 18.0 landed
-
Support loading of injection points
- 4b211003ecc2 18.0 landed