Re: isolation tester limitation in case of multiple injection points in a single command
Mihail Nikalayeu <mihailnikalayeu@gmail.com>
From: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-09T12:53:00Z
Lists: pgsql-hackers
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? Like 'wait' and 'notice' (tol be executed in order they registered). It feels like a pretty simple solution and covers my needs. Best regards, Mikhail. [0]: https://github.com/postgres/postgres/blob/7b2eb72b1b8ce4279e42848a3978e781ae239355/src/backend/utils/misc/injection_point.c#L298-L301
Commits
-
Improve test case stability
- 417ac9c1eeeb 19 (unreleased) landed
-
injection_points: Add injection_points_list()
- 4eca711bc991 19 (unreleased) cited
-
Add InjectionPointList() to retrieve list of injection points
- 7b2eb72b1b8c 19 (unreleased) cited