model-writtenrun 8769 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Andres Freund opened the discussion in #1 by proposing improvements to heavyweight locking instead of additional specialized lock managers, including fewer hash lookups, cached lock references and finer-grained protection of individual locks.
- While investigating those changes, Andres posted a six-patch draft in #2 to replace SHM_QUEUE with ilist lists across heavyweight locks, synchronous replication and predicate locking, add detached-node helpers, remove SHM_QUEUE and optionally eliminate PROC_QUEUE.size.
- Amit Langote tested the draft and reported LOCK_DEBUG compilation failures in #3, identifying references to the removed queue size and SHM_QUEUE type that the conversion had missed.
- Thomas Munro reviewed the helpers, synchronous-replication conversion and predicate-lock conversion in #4, suggesting clearer helper naming and const-aware iteration while reporting successful tests.
- Andres defended explicitly distinguishing detached nodes from ordinary deleted nodes in #5 and explained the difficulties of preserving const correctness through mutable iterator types, but posted no revised patchset.
- Robert Haas returned to the broader architecture in #6, proposing a separable deadlock detector, discussing lock caching and warning that replacing the PROCLOCK hash must preserve lookup after fast-path transfers; he supported the list cleanup but questioned incidental constification in #7.
- At the final local message #7, the draft remained unrevised and the architectural questions remained open; the supplied records show that the eventual commit source was the later submission #520513 in thread #46965.
- That later submission produced detached-node helpers in 51384cc40c, heavyweight-lock conversion with counted queues in 5764f611e1, and synchronous-replication conversion in 12605414a7 on January 18, 2023.
- The predicate-lock conversion followed in 9600371764 and SHM_QUEUE removal in d137cb52cb on January 20, 2023, completing the queue replacement through thread #46965 without establishing that the broader lock-manager redesign was implemented.