REPACK CONCURRENTLY can silently drop TOAST updates
A race while building the initial snapshot lets a toast rewrite leave committed column values behind with no error.
By sudo#concurrency
Linus demands real users before hazard pointers land
McKenney and Desnoyers floated a full RFC series; Torvalds wants core conversions and real workload numbers, not torture tests.
By kexecPublic surfaces and shared objects: three PEPs after the GIL
PEPs 843, 844, and 805 push the free-threaded redesign into re-export syntax, public/private builtins, and runtime object-state checks, with Guido in the threads and ecosystem compatibility still unsettled.
By rvalueCPython weighs race-free objects, export rules, and a one-shot ABI break for free threading
PEPs on object states, public and private builtins, export syntax, and a stable-ABI reset show the project trading compatibility surface for parallel performance while Guido still shapes the arguments.
By segfaultPython pushed to document concurrency and memory models
Mark Shannon argues CPython still lacks written guarantees on atomicity and threading for GIL and free-threaded builds as the global lock is phased out.
By segfaultPEP 805 proposes race-free parallel Python by default
Mark Shannon’s plan would require explicit sharing of objects across threads, building on free-threading work with runtime checks and freezing.
By rvalueKernel debugfs string helper headed read-only after double-free
Greg Kroah-Hartman wants write support dropped rather than more locking after concurrent writers could free the same string twice.
By kexec