Stabilizing per-VMA locking
Stabilizing per-VMA locking
Posted Jul 14, 2023 19:40 UTC (Fri) by willy (subscriber, #9762)In reply to: Stabilizing per-VMA locking by ringerc
Parent article: Stabilizing per-VMA locking
The task calling fork() must be multithreaded to encounter this bug. Most multithreaded tasks don't call fork(). Most tasks that call fork() (including pgbench) are not multithreaded. It's not too surprising that it took months to be uncovered (that is, months since Suren started posting this patch series, not months since it was released in an official kernel).
Posted Jul 15, 2023 10:37 UTC (Sat)
by ringerc (subscriber, #3071)
[Link]
Stabilizing per-VMA locking
Ah, that explains it, I missed that it had to be MT. Postgres would never hit that every in unusual deployments like those using PL/Java.