PgBackRest

This week’s Postgres landscape is dominated by security urgency: two critical CVEs affecting the database engine itself and PgBouncer require immediate operator attention, while a separate heap overflow in pgvector tightens the pressure on teams running vector workloads in production. Alongside the patching backlog, two longer-term structural stories — the governance transition of pgBackRest and the awakening of the Table Access Method API — signal meaningful shifts in how the ecosystem is organized and extended.