Re: isolation tester limitation in case of multiple injection points in a single command

2025-11-09 Thread Michael Paquier
On Sun, Nov 09, 2025 at 11:51:51PM +0100, Mihail Nikalayeu wrote: > Yes, possible. But the idea is to avoid weird two INJECTION_POINT in a > row... FWIW, I think that it's OK to use as style. The backend-side injection point implementation is currently quite simple, meaning that it less prone to

Re: isolation tester limitation in case of multiple injection points in a single command

2025-11-09 Thread Mihail Nikalayeu
Hello! нд, 9 ліс 2025, 23:34 карыстальнік Michael Paquier напісаў: > It is already possible to achieve that, isn't it? One can define > side-by-side twice INJECTION_POINT(), then assign a different callback > to each with a strict control of the execution order. > Yes, possible. But the idea i

Re: isolation tester limitation in case of multiple injection points in a single command

2025-11-09 Thread Michael Paquier
On Sun, Nov 09, 2025 at 01:53:00PM +0100, Mihail Nikalayeu wrote: > What if we extend that limitation to allow registration of different > types for the same injection point? Like 'wait' and 'notice' (tol be > executed in order they registered). > It feels like a pretty simple solution and covers m

Re: isolation tester limitation in case of multiple injection points in a single command

2025-11-09 Thread Mihail Nikalayeu
Hello, Michael! Currently injection_point.c says [0]: > /* > * Allocate and register a new injection point. A new point should not > * exist. For testing purposes this should be fine. > */ What if we extend that limitation to allow registration of different types for the same injection point?

Re: isolation tester limitation in case of multiple injection points in a single command

2025-10-20 Thread Mihail Nikalayeu
Hello, Michael! Michael Paquier : > Ah, OK. So you want to have one single command, still wait through > two injection points inside it. I am wondering about one thing: do > you really require that? Could it be simpler to have two > permutations, each one of them using one wait point to check y

Re: isolation tester limitation in case of multiple injection points in a single command

2025-10-19 Thread Michael Paquier
On Sun, Oct 19, 2025 at 03:41:00PM +0200, Mihail Nikalayeu wrote: > Hello, everyone! > > While stabilizing tests for [0] I realized I have no idea how to set > up a pretty simple scenario using an isolation tester. > > It looks like this: > * session S1 start long running query (CREATE INDEX CONC

isolation tester limitation in case of multiple injection points in a single command

2025-10-19 Thread Mihail Nikalayeu
Hello, everyone! While stabilizing tests for [0] I realized I have no idea how to set up a pretty simple scenario using an isolation tester. It looks like this: * session S1 start long running query (CREATE INDEX CONCURRENTLY) and traps into injection point X * session S2 executes some command *