Re: isolation tester limitation in case of multiple injection points in a single command - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: isolation tester limitation in case of multiple injection points in a single command
Date
Msg-id CADzfLwUup8U3a-fXrDiQwQkan1pmJwcybPe45Sn1Yf1v49ZeYA@mail.gmail.com
Whole thread Raw
In response to Re: isolation tester limitation in case of multiple injection points in a single command  (Mihail Nikalayeu <mihailnikalayeu@gmail.com>)
Responses Re: isolation tester limitation in case of multiple injection points in a single command
List 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



pgsql-hackers by date:

Previous
From: Mihail Nikalayeu
Date:
Subject: Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Next
From: Tom Lane
Date:
Subject: Re: pg_dump not dumping default_text_search_config WAI?