fix(postgres): chat history slows under concurrent reads (#190129) - PostgreSQL history workers spend most of a request blocked on bridge replies, so the shared two-worker reader cap queued concurrent chat.history requests while CPU sat idle. - History on PostgreSQL agent stores now uses two workers per CPU above one, capped at four. SQLite and unset engines keep the reader size. - The history pool resolves its size on first use, because boot installs the database engine after the lane module is imported. - Transcript search and the other transcript lanes are unchanged. - Tests: per-engine sizing table, and a lane test that installs the engine after import (PostgreSQL 4, SQLite 2). - Docs: runtime architecture sizing note and the PostgreSQL backend budget.
fix(postgres): chat history slows under concurrent reads (#190129)
Find Your Interest
- Android Dev Summit 2026
- How do you fact-check an AI?
- Apple’s rumored glasses need a Siri AI I can actually rely on
- Build your way: Use any AI agent of your choice in Android Studio
- The Agentic Web
- When your AI agent publishes internal data
- Intelligence analysis platform for AI Agents (~OpenClaw)
- Siri is a Gemini
- AI agents are invading your PC
- Bring back the iBook, you cowards





