Read-Only Postgres Access Can Still Crash Your App

A read-only Postgres connection does not guarantee safety—exploratory queries, large aggregates, and concurrent retries can still exhaust CPU, memory, and I/O. Treat AI database traffic as a separate workload class with dedicated roles, bounded connection pools, and strict limits. Replicas are not free capacity; they require operational budgets for lag and I/O.