← All digests

DBMS Weekly — 2026-06-07 (week of 2026-06-01–2026-06-07)

PostgreSQL

  • PostgreSQL 19 Beta 1 released — first beta of PG19 lands (June 4) with in-core REPACK [CONCURRENTLY], the pg_plan_advice/pg_stash_advice planner-stabilization extensions, parallel autovacuum (autovacuum_max_parallel_workers) plus a new vacuum-prioritization heuristic, and adaptive async-I/O worker scaling (io_min_workers/io_max_workers) building on PG18. (Jonathan Katz · postgresql.org)
  • Looking forward to Postgres 19: query hints, sort of — a tour of PG19's new pg_plan_advice / pg_stash_advice contrib modules that capture and reapply planner decisions by query id, ending the project's long "no hints" posture without actually being hints. (Shaun Thomas · pgEdge)
  • pg_durable: durable execution as a Postgres extension — Microsoft open-sources a pgrx/Rust extension that runs Temporal-style durable functions entirely inside Postgres: state checkpointed to tables, crash/failover recovery via deterministic replay, a SQL DSL (~>, |=>), and a background worker — no Redis, no external orchestrator. Preview, PostgreSQL 17. (microsoft/pg_durable)
  • The integer at the end of the universe: integer overflow in Postgres — what actually happens when an int4 sequence runs out of headroom, how to spot it before it bites, and how to migrate to bigint without a full-table-rewrite outage. (Crunchy Data)
  • Async I/O in PostgreSQL 19: the year after — Christophe Pettus revisits the io_uring/AIO subsystem one release on, covering the new auto-scaling worker model and what changed for operators between 18 and 19. (thebuild.com)
  • Handling graphs with SQL/PGQ in PostgreSQL — worked examples of the ISO SQL/PGQ property-graph syntax (CREATE PROPERTY GRAPH, GRAPH_TABLE) shipping in PG19, run over ordinary relational tables. (Cybertec)
  • PostgreSQL and the OOM killer: why we use strict memory overcommit — Ubicloud argues for vm.overcommit_memory=2 so allocations fail predictably instead of the kernel killing a random backend (often the postmaster) under memory pressure. (Lev Kokotov · ubicloud.com)
  • Authenticate PostgreSQL with SSH keys — a PAM module that lets Postgres verify connections against users' existing SSH public keys, reusing key infrastructure you already manage instead of yet another credential store. (ChronicallyJD)

Community pulse

Wider DBMS & distributed data

Migration experience

International (non-English sources)

  • 2 + 2 = 6: fixing lost updates in Postgres — a systematic tour of race conditions under each isolation level with measured costs of each fix (SELECT FOR UPDATE, advisory locks, SERIALIZABLE, atomic UPDATE) on a real highload workload. (nikolayschaback · Habr) [ru] (orig: «2 + 2 = 6 и как мы это фиксим: lost updates в Postgres»)
  • Killing the REFRESH MATERIALIZED VIEW queue in PostgreSQL — SKB Kontur's hour-long MV refreshes were piling into a connection-hogging queue; they used pg_try_advisory_xact_lock per-MV plus trigger-tracked dependencies so a redundant REFRESH skips instead of waiting. (makushevski · Habr / SKB Kontur) [ru] (orig: «Как мы убрали очередь из REFRESH MATERIALIZED VIEW в PostgreSQL»)
  • VARCHAR(N) in PostgreSQL is a constraint, not a memory saving — myth-busting the varchar(255) habit: Postgres stores the actual string regardless of the limit, so N buys you a check constraint, not packed storage; when it helps and when it's cargo-culted. (alwaysdeterminated · Habr) [ru] (orig: «VARCHAR(N) в PostgreSQL: ограничение, а не экономия памяти»)

Call for papers

18 items · sources scanned: ~30 · community threads scanned: Hacker News (Algolia, postgres+database queries) · international: Habr [ru] in-window; Dalibo [fr] and Qiita [ja] had no in-window items · filtered out as marketing/ads: ~14