Re: Adding facility for injection points (or probe points?) for more advanced tests - Mailing list pgsql-hackers

From Amul Sul
Subject Re: Adding facility for injection points (or probe points?) for more advanced tests
Date
Msg-id CAAJ_b94ujb9Y6+csX82X1WPAEqSTAjFrPUgfkEDRrZLOOia_yg@mail.gmail.com
Whole thread Raw
In response to Adding facility for injection points (or probe points?) for more advanced tests  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Adding facility for injection points (or probe points?) for more advanced tests
List pgsql-hackers


On Wed, Oct 25, 2023 at 9:43 AM Michael Paquier <michael@paquier.xyz> wrote:
Hi all,

I don't remember how many times in the last few years when I've had to
hack the backend to produce a test case that involves a weird race
condition across multiple processes running in the backend, to be able
to prove a point or just test a fix (one recent case: 2b8e5273e949).
Usually, I come to hardcoding stuff for the following situations:
- Trigger a PANIC, to force recovery.
- A FATAL, to take down a session, or just an ERROR.
- palloc() failure injection.
- Sleep to slow down a code path.
- Pause and release with condition variable.

+1 for the feature.

TWIMW, here[1] is an interesting talk from pgconf.in 2020 on the similar topic.


Regards,
Amul Sul 

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Adding facility for injection points (or probe points?) for more advanced tests
Next
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby