Re: Can can I make an injection point wait occur no more than once?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Can can I make an injection point wait occur no more than once?
Date: 2025-07-08 15:21:20
Message-ID: CAH2-Wzn=13H=EsRoroKx5DZ0ffvWSO_9KX6suGenyMpOAMHCWg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 7, 2025 at 9:53 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> If it continues to be a problem, consider sharing the patch that's behaving
> this way for you.

Attached patch shows my current progress with the isolation test.

I also attach diff output of the FreeBSD failures. Notice that the
line "backwards_scan_session: NOTICE: notice triggered for injection
point lock-and-validate-new-lastcurrblkno" is completely absent from
the test output. This absence indicates that the desired test coverage
is totally missing on FreeBSD -- so the test is completely broken on
FreeBSD.

I ran "meson test --suite setup --suite nbtree -q --print-errorlogs"
in a loop 500 times on my Debian workstation without seeing any
failures. Seems stable there. Whereas the FreeBSD target hasn't even
passed once out of more than a dozen attempts. Seems to be reliably
broken on FreeBSD.

Thanks
--
Peter Geoghegan

Attachment Content-Type Size
regression.txt text/plain 1.6 KB
0001-injection-points.patch application/octet-stream 7.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-07-08 15:21:22 Re: like pg_shmem_allocations, but fine-grained for DSM registry ?
Previous Message Matheus Alcantara 2025-07-08 15:20:54 Re: POC: Parallel processing of indexes in autovacuum