| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| 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 01:53:44 |
| Message-ID: | 20250708015344.06.nmisch@google.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 07, 2025 at 09:40:20PM -0400, Peter Geoghegan wrote:
> I'm finding that the FreeBSD Meson CI target consistently fails with
> this setup, though. And with just about any variant I can think of;
> seems to fail quite reliably. The initial SELECT backwards scan
> statement will complete without ever waiting (though only on CI).
>
> Do you know what that might be? It would be a lot easier if there was
> at least a way to debug this locally.
FreeBSD's scheduler is different enough to exercise quite-different relative
timings of process wake-up. I got a lot of FreeBSD failures when my tests had
underspecified the order of events.
If it continues to be a problem, consider sharing the patch that's behaving
this way for you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2025-07-08 01:55:00 | Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach |
| Previous Message | Cédric Villemain | 2025-07-08 01:47:00 | Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach |