Keeping Vector Retrieval Stable While Your Knowledge Base Is Still Loading

At 3:17 AM, your agent platform stops responding. Ingestion workers are retrying document chunks. Retrieval latency has spiked from 80ms to 4 seconds. The HNSW index is fine. The problem is that ingestion and retrieval are fighting over the same PostgreSQL pages, and neither path has backpressure logic. This is the production failure that tutorials skip.

I am evaluating Tencent/WeKnora as an external integrator, using its stated document-to-RAG, agent, and self-maintaining Wiki scope. The design below is a proposed PostgreSQL retrieval boundary, not a claim about WeKnora's current implementation or measured performance.

Keep ingestion outside the answering path

Separate document parsing, chunking, and embedding into asynchronous workers. Those workers write versioned chunks into PostgreSQL.…