PostgreSQL Community Debates: To Thread or Not to Thread?
The PostgreSQL community is currently debating a potential shift from the current process-based design of the database to a more modern, threaded design. While some members of the community believe this would provide benefits such as increased performance and better resource utilization, others like Tom Lane are concerned about the potential for disaster.
Lane warns that there is far too much code that would get broken, largely silently, and much of it is not under their control. He cites the cautionary tale of PHP 6, which led to years of wasted time and stagnation for the language. Lane’s concerns are echoed by other members of the community who worry that the shift to a threaded design would require rewriting much of the code base, which would take extensive time and resources.