Re: Injection points: preloading and runtime arguments
| От | Andrey M. Borodin |
|---|---|
| Тема | Re: Injection points: preloading and runtime arguments |
| Дата | |
| Msg-id | F5CA5FD7-4731-4663-8A05-8B641CF11CA6@yandex-team.ru обсуждение исходный текст |
| Ответ на | Re: Injection points: preloading and runtime arguments (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Injection points: preloading and runtime arguments
|
| Список | pgsql-hackers |
> On 5 Jun 2024, at 03:52, Michael Paquier <michael@paquier.xyz> wrote:
>
> Another thing you could do is to define a
> INJECTION_POINT_LOAD() in the code path you're stressing outside the
> critical section where the point is run. This should save from a call
> to the SQL function. This choice is up to the one implementing the
> test, both can be useful depending on what one is trying to achieve.
Thanks!
Interestingly, previously having INJECTION_POINT_PRELOAD() was not enough.
But now both INJECTION_POINT_LOAD() or injection_points_load() do the trick, so for me any of them is enough.
My test works with current version, but I have one slight problem, I need to call
$node->safe_psql('postgres', q(select injection_points_detach('GetMultiXactIdMembers-CV-sleep')));
Before
$node->safe_psql('postgres', q(select injection_points_wakeup('GetMultiXactIdMembers-CV-sleep')));
Is it OK to detach() before wakeup()? Or, perhaps, can a detach() do a wakeup() automatically?
Best regards, Andrey Borodin.
В списке pgsql-hackers по дате отправления: