OpenClaw: PostgreSQL Goes Supported Amid Major Cleanup
PostgreSQL 16 through 18 is now qualified as a supported store with stable migration and credential fixes, while a broad refactor sweep removes dead code and cuts UI and database overhead with no intended behavior change.
Duration: PT2M40S
Episode overview
This episode is a short developer briefing from OpenClaw.
It explains recent repository work in plain language.
- Show: OpenClaw
- Published: 2026-10-20T06:04:50Z
- Audio duration: PT2M40S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's Tuesday, October 20th, 2026, and this is your OpenClaw developer briefing.
The lead story is PostgreSQL moving from experimental to a supported alternative, with the stable migration path repaired, paired with a sweeping internal cleanup to reduce overhead.
First, Postgres stabilization. In PR 178005 and PR 177922, setup, Doctor, status and configuration help now document PostgreSQL 16 through 18 with full conformance runs, covering mixed engines, gateway and command-line flows, and memory search. The same work repairs the stable SQLite to current to Postgres adoption…
Second, dead code and UI performance. Across more than twenty refactors, the team removed unobserved event producers, unused plugin arguments, retired channel collectors for Discord and WhatsApp, and duplicate lifecycle owners. For the Control UI, that means trusting leaf owners, inlining single-use chat…
Third, visible polish and pending providers. Merged PR 178084 shows sidebar shortcuts as keycap chips instead of parenthesized text, and PR 178061 fixes a temporary session row flashing in Show All mode. Two open fixes to watch are PR 178130 to cap Qianfan memory embedding batches at 16 inputs, and…
W…
Nearby episodes from OpenClaw
- Gateway Resilience and CLI Backend Stability
- Honest Failures, Smarter Tool Checks, and Memory Cuts
- Restart Recovery Hardening
- Solid UI Cleanup and Repair Reliability
- Automation Isolation and Public GitHub Access
- Gateway Recovery, Resilient Turns, and Channel Fixes
- Credential Guardrails and Cutting Wasted Work
- Pairing Isolation and Startup Trim