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

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: isolation tester limitation in case of multiple injection points in a single command
Date: 2025-11-09 12:53:00
Message-ID: CADzfLwUup8U3a-fXrDiQwQkan1pmJwcybPe45Sn1Yf1v49ZeYA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-11-09 16:03:31 Re: pg_dump not dumping default_text_search_config WAI?
Previous Message Mihail Nikalayeu 2025-11-09 11:20:11 Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY