The only backup that counts is one you have restored
A backup file you have never restored is a hope, not a backup. A short restore drill for small servers, and the two database mistakes it catches most often.
Topic · 33 stories · page 2 of 2
33 stories tagged postgresql on AI Tamer, newest first.
A backup file you have never restored is a hope, not a backup. A short restore drill for small servers, and the two database mistakes it catches most often.
JVN#22475874 (2026-09-29): seven Pgpool-II CVEs; lead CVE-2026-92867 authenticated OOB write (CVSS 4.0 8.7 / 3.0 8.8)—process termination and arbitrary code execution. Fixed in 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21.
Radim Marek (boringSQL, Sep 28) benches PostgreSQL 19beta4 core REPACK (CONCURRENTLY) vs pg_repack/pg_squeeze: WAL, disk, cluster-wide VACUUM hold-back, ~105M change ceiling, and MVCC caveats—author benches only.
Google Cloud AlloyDB “PostgreSQL for agents” (docs updated Sep 24, 2026) is Preview only: agents query live transactional data with isolation from core systems and can scale compute to zero when idle.
MySQL and MariaDB now document native vector features, PostgreSQL can use pgvector, and SQLite can add search through extensions. Here is how to choose by deployment shape and retrieval needs.
PgBouncer 1.26.0 (Sep 23, 2026) fixes CVE-2026-19888, CVE-2026-6668, and CVE-2026-6669 (DoS only: crash, infinite loop, unbounded login work; no RCE or CVSS). Also: pool_idle_timeout and query_wait_timeout; -R removed.
Databricks GA’d Lakebase Search on AWS/Azure (blog 2026-09-28): lakebase_vector (ANN) + lakebase_text (BM25) in the same serverless Postgres OLTP—hybrid via RRF, no separate search cluster. VectorDBBench/Conexiom figures are vendor-reported.
AWS GA’d direct Iceberg/Parquet lake queries from Aurora PostgreSQL (2026-09-30) via embedded DuckDB and aurora_analytics—no ETL. Join live ops rows (incl. uncommitted) with the lake. PG 17.11+/18.6+; no extra feature fee (compute + S3).
pgvector, JSONB, full-text search and row security can support an AI app in one PostgreSQL database, with practical limits to measure before you scale.