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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
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 22:34:21
Message-ID: aREW7Qo0GqjfiHn7@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 my needs.

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mihail Nikalayeu 2025-11-09 22:51:51 Re: isolation tester limitation in case of multiple injection points in a single command
Previous Message Thomas Munro 2025-11-09 22:20:38 Re: Don't synchronously wait for already-in-progress IO in read stream