Multi-threaded PostgreSQL?
summary
A pgsql-hackers thread launched in June proposing a full switch from a 1990s multiprocess model to threads; no production patch exists yet, only a preliminary refactor and a commitfest patch that annotates globals. Key steps: convert roughly 2,000 global variables to session-local or thread-local, build a static-analysis tool, replace dynamic shared memory patterns, add an extension control flag to mark thread safety, and provide a GUC mode to run either threads or processes during a short transition.
AI-written summary · about
chapters (9)
- 0:00Motivation for threading
- 3:26Architectural comparison
- 7:18Benefits of multithreading
- 9:21Addressing design objections
- 14:00Managing risks and trade-offs
- 18:01Precedents in other projects
- 22:12Implementation requirements
- 30:11Transition and future vision
- 36:56Action plan and Q&A
related talks
52mMulti-threaded PostgreSQL?
46mInvestigating Multithreaded PostgreSQL
50mHacking on Postgres: An Overview
30mPostgreSQL and Linux Kernel interactions
26mRethinking PostgreSQL Performance in the Age of Monster Hardware
27mHow Do We Get Postgres to the Next Level?
21mA Walking Tour of PostgreSQL
42mPostgreSQL is Nowhere Near Ready