← All digests

DBMS Weekly — 2026-11-09 (week of Nov 9–15)

The Nov 12 update releases fixed 52 CVEs and over 140 bugs, closed out PostgreSQL 14, and shipped 19 RC 2 ahead of a Nov 19 GA. The CVE-2026-6460 fix versions composite datums, which breaks the extension ABI, so packagers now pin extensions to the new server libs. The list kept landing wrong-result fixes in Memoize, initplans, FULL JOIN and GROUP BY removal, while an auto_explain crash will ship in 19.0 behind the release freeze. On the blogs: pg_orca's PostgreSQL-aligned cost model, a glibc collation corruption catalogue, and three migration reports from Heroku, pgvector and Azure.

PostgreSQL

  • PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2 — Fixes 52 CVEs, led by CVE-2026-6460's type confusion after ALTER … SET DATA TYPE, and 140+ bugs; 14.25 is the last 14.x. After updating, REINDEX suspect GIN, gist_trgm_ops and bpchar B-tree indexes, check partitioned NOT NULL NO INHERIT constraints, and take a fresh full backup before further incrementals. (PostgreSQL Global Development Group · pgsql-announce) [release]
  • November minor releases: update the server and extensions together — The CVE-2026-6460 fix turns DatumGetHeapTupleHeader() into a server function with a new heap_datum_check(), so every PGDG RPM extension now requires postgresql18-libs >= 18.7. (Devrim Gündüz · PGDG RPM packager)
  • Postgres 18.7 minor breaks ABI compatibility again — New AGE, credcheck and pg_cron builds already fail on 18.6, so server and extensions must move in lockstep; a follow-up shows apt and dnf now refuse the mismatched install. (Jeremy Schneider · ardentperf.com)
  • The impact of CVE-2026-6460 and the other memory-corruption fixes — Sorts the 52 CVEs by what an attacker needs, from a pre-auth cancel-request spinlock leak that restarts an 18 server to tsvector heap overflows any user can reach. (Lukas Fittl · pganalyze) [vendor blog — substantive]
  • Turning a 22-year-old type-confusion primitive into RCE (CVE-2026-6460) — Change a field's type inside a stored composite value, read it back, and the mismatch becomes a reliable memory-corruption primitive; HN argued whether an exploit needing a login counts as RCE. (Mehmet Ince · mehmetince.net; HN 232 pts, 40 comments)
  • What LLMs do to PostgreSQL and DBAs — Three years of list counts: new pgsql-bugs reports climb from mid-July 2026 while pgsql-general shrinks, and Postgres IRC fell from ~5,900 messages a month in 2024 to ~700. (Hubert 'depesz' Lubaczewski · depesz.com)
  • Pricing plans in PostgreSQL's currency: pg_orca's PG-aligned cost model — Ports costsize.c into the ORCA optimizer extension, mapping ORCA's total-only costs and rebinds onto startup cost and loop_count; a 311-EXPLAIN harness keeps 183 of 188 same-shape plans within 2%. (Jianghua Yang · agentml.ai)
  • LSN consistency for the extended protocol: an in-band wait message — Rewriting a SET prefix can't work for prepared statements, so the proxy negotiates a new W protocol message that carries a read-your-writes LSN wait ahead of Parse/Bind on replicas. (Semyon Binev · Awide Labs) [vendor blog — substantive]
  • Ten ways a glibc change can break your PostgreSQL cluster — A Rocky 8.9 primary with a Rocky 9.3 replica on sv_SE, where W stops sorting with V, reproduces ten corruption cases, including unique indexes that admit duplicates. (Pablo Svampa · Percona) [vendor blog — substantive]
  • B-tree pages, sorted and sparse — A pageinspect walk on 18.6: delete 80% of rows, VACUUM, reinsert, and the heap stays at 443 pages while the index grows from 276 to 385 (the primary key to 496). (Radim Marek · boringsql.com)
  • Building a table access method, part 8: cache invalidation — Relcache invalidation callbacks let backends that never touched a dropped or truncated table release its DSM arena, and why the callback may only record work for transaction end. (Mats Kindahl · dbmsdrops.kindahl.net)
  • json vs jsonb: size and speed, measured — On 17.11 and 18.6, jsonb ranged from 22.6% smaller to 40.9% larger than json depending on whitespace, shape and compression, while ->> reads ran 2.7–10.6× faster. (Chris van Eijk · now-next.nl)
  • A database per git worktree that barely uses any disk — PG 18's file_copy_method = clone gives copy-on-write template databases on APFS, Btrfs, XFS and ZFS, but only with STRATEGY = FILE_COPY; the default WAL_LOG strategy silently ignores it. (Dennis Paagman · paagman.dev)
  • Two migrations collide: one loud failure, one silent one — Two branches' CREATE INDEX IF NOT EXISTS with the same name but different definitions both succeed, leaving environments with divergent indexes and identical migration histories. (Maki Majima · diffy-pick.com)
  • Fixing Postgres's biggest mistakes — pgrust's plan for VACUUM, connections, bad plans and jsonb statistics; its first feedback-driven planner made a Join Order Benchmark query 10× slower by "fleeing from knowledge to ignorance". (Michael Malis · malisper.me) [unverified: prototype numbers unpublished]
  • pg_fastload 1.0.0 — A BSD-licensed pg_bulkload fork that moves reading, parsing and tuple forming into background workers over shm_mq while the leader inserts in one transaction. A 1 GiB lineitem CSV loads in 1.37 s with 15 workers versus 8.32 s for COPY FROM; unsupported options fall back to serial. (yuansong · pgsql-general) [release]
  • PostgreSQL buildfarm client release 22 — Adds a config-driven PGXSExtension module for testing out-of-tree extensions and UNRELEASED/HEAD_PLUS_UNRELEASED branch tags. PatchStack animals now apply series through the patches repo's import-series.pl, so the farm tests exactly what a release wrap produces. (Andrew Dunstan · adpgtech.blogspot.com) [release]
  • Dasha 1.10 — The agentless, read-only fleet dashboard discovers Patroni clusters from etcd v3 and Consul and samples pg_stat_activity every 1–10 s into a wait-event view (PG 14+). New: a per-slot forecast of time to max_slot_wal_keep_size invalidation from the measured WAL rate. (pgsql-announce) [release]

PostgreSQL mailing lists

  • [committers] Introduce attribute versioning to prevent unsafe deforming — The CVE-2026-6460 fix stores the version as an internal attribute option in back branches, which crashed TimescaleDB until a workaround, and as pg_attribute.attversion in master. (Andres Freund · pgsql-committers) [committed]
  • [hackers] auto_explain crashes on EXPLAIN (BUFFERS) of an index scan — EXPLAIN (BUFFERS) without ANALYZE under auto_explain's log_analyze crashes in show_indexscan_info() on 19rc2; the fix waits until after 19.0 because the branch is frozen. (Xiaoxuan Li; Peter Geoghegan · pgsql-hackers) [open]
  • [hackers] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting — 19's on-access pruning sets pages all-visible, so the next VACUUM extrapolated from a tiny tail and could zero reltuples; four fixes landed before GA. (Vaibhav Jain; Melanie Plageman · pgsql-hackers) [committed]
  • [hackers] WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts — The default strategy logs VM and FSM pages as standard pages whose "hole" spans their whole content, so replay restores them as zeros; bug #19894 hit it independently this week. (Matthias van de Meent; Melanie Plageman · pgsql-hackers) [patch posted]
  • [committers] Fix Memoize using the wrong equality operator for cache keys — A stricter join operator over a case-insensitive collation got another key's cached rows; a second fix stops simplehash deletions moving the just-inserted entry. (David Rowley · pgsql-committers) [committed]
  • [hackers] Wrong results with initplans moved by setrefs.c — Removing a trivial SubqueryScan or single-child Append left the moved initplans' Params out of the child's extParam, so rescans reused stale values; an LLM-fuzzer find, back-patched to 15. (Richard Guo; David Rowley · pgsql-hackers) [committed]
  • [hackers] reconsider_full_join_clause and NULL-preserving COALESCE arguments — Vondra committed a fix for FULL JOIN constant propagation with reversed ON operands; non-NULL-preserving COALESCE arguments still need a walker-based patch. (Tomas Vondra; Kirill Reshke · pgsql-hackers) [patch posted]
  • [hackers] Wrong results from GROUP BY column removal — Since 18, a NULLS NOT DISTINCT unique index let the planner drop other GROUP BY columns, merging null-extended outer-join rows with a real NULL row; fixed back to 18. (Richard Guo · pgsql-hackers) [committed]
  • [bugs] #19861: self-join elimination drops a VOLATILE predicate — 18's self-join elimination turns f(a.id) and f(b.id) into one expression, calling a volatile function once; the patch skips such joins, but nextval() in the target list still misbehaves. (Tender Wang; Kirill Reshke · pgsql-bugs) [patch posted]
  • [bugs] #19892: logical replication skips rows with NULL in a hash-indexed subscriber column — Under REPLICA IDENTITY FULL, apply-side lookups through a hash index miss NULL rows, so UPDATE and DELETE are silently skipped and replicas diverge; the patch falls back to a seqscan. (Nisha Moond · pgsql-bugs) [patch posted]
  • [bugs] Lost walsender wakeup stalls synchronous commits — Last issue's physical-walsender race also exists in the logical walsender's WalSndWaitForWal() and in WaitForStandbyConfirmation() (17+). (Alex Speller; Fujii Masao, Xuneng Zhou · pgsql-bugs) [open]
  • [hackers] Crashes on a partition whose concurrent detach never finished — Logical decoding crashed on any change to a partition left detach-pending by an interrupted DETACH … CONCURRENTLY; fixed back to 15, follow-ups pending. (Mihail Nikalayeu; Amit Kapila · pgsql-hackers) [committed]
  • [bugs] #19897: recovery fails after "consistent recovery state reached" — A base backup taken from a standby sometimes fails to start; the obvious fix broke pg_last_xact_replay_timestamp(), the next broke promotion, and v3 avoids both. (Haruka Takatsuka; Zsolt Parragi · pgsql-bugs) [patch posted]
  • [hackers] Two statement_timeout race conditions — A timeout expiring at command end can cancel the next command, one during parsing reports "user request", and reviewers found lock_timeout leaking out of COMMIT the same way. (Tomas Vondra; Zsolt Parragi · pgsql-hackers) [patch posted]
  • [hackers] SIGFPE handling — Heikki wants FloatExceptionHandler in every process and a PANIC, since an ERROR under an LWLock can leave shared memory half-updated; Tom Lane agrees on the first and is "violently against" the second. (Heikki Linnakangas; Tom Lane · pgsql-hackers) [open]
  • [hackers] Recovery does not honor io_combine_limit — The author's own benchmark undercut his WAL read-ahead patch: on a 3,000-IOPS gp3 volume, raising read_ahead_kb to 256 gave the same ~25% fewer reads and ~6% faster redo. (Mats Kindahl; Andrey Borodin · pgsql-hackers) [needs review]
  • [hackers] Planner bug causes incorrect results in PG14 and PG15 — A join_clause_is_movable_into() wrong-result bug, gone since 16's infrastructure rework, will likely stay in 15: Tom Lane is "unexcited" about a localized back-branch fix. (Tom Lane · pgsql-hackers) [open]
  • [committers] Index pg_constraint.confrelid to avoid seqscans — Since not-null constraints became pg_constraint rows, ATTACH/DETACH PARTITION and pg_upgrade seqscan an ever-larger catalog; master gains an index, though FK-related TRUNCATE still seqscans. (Manuel Reyes Bravo; Álvaro Herrera · pgsql-committers) [committed]
  • [hackers] BGWORKER_INTERRUPTIBLE workers are never restarted — Resolved since last issue: such workers are now signalled directly instead of unregistered, so they restart per bgw_restart_time (19 and master). (Xuneng Zhou; Michael Paquier · pgsql-hackers) [committed]
  • [committers] Drop support for named POSIX semaphores — The sem_open() implementation never worked with EXEC_BACKEND, cost a file descriptor per semaphore per backend, and no platform prefers it; gone from master. (Tom Lane · pgsql-committers) [committed]

CommitFest (open: PG20-4, #63 · in progress: PG20-3, #62)

  • Balance (Nov 9–15): 30 new · 17 closed (13 committed / 3 withdrawn / 1 returned with feedback) → net +13 (vs +20 last week; complete counts). Every new entry went to PG20-4; 22 promotions to Ready for Committer. Active at scan (Nov 16): PG20-3 548 (373 needs review / 50 waiting on author / 125 ready for committer), PG20-4 69.
  • New this week: Speed up hash join builds by linking tuples into buckets in groups (Tatsuya Kawata) — after copying a tuple it prefetches the bucket header and links queued tuples 32 at a time once the bucket array reaches 512 kB; a 3 M-row build fell from 743 to 479 ms, and grouping alone, without prefetch, gave most of it. Also Keep TIDBitmap pagetable memory across bitmap scans (#7617), Eliminate redundant outer-join clone clauses after constant propagation (#7615), Improvements / reworks for FDW insert batching (#7631), transaction_timeout is not enforced during ClientWrite (#7632).
  • Closed: committed [PG19] Wrong results from NOT NULL-based expression simplification (#7400), [PG19] Wrong results from Memoize with a nondeterministic collation (#7421), [PG19] Eager aggregation runs a volatile join clause once per group (#7448), WAL record CRC calculated incorrectly because of underlying buffer modification (#7532), ATTACH PARTITION cost grows with pg_constraint size (#7365) and 8 more; withdrawn #6449, #7610 and a duplicate; returned with feedback Fix rare recovery shutdown hang (#4884).

Community pulse

  • How did Postgres displace MySQL? — Practitioners date the flip a decade back, crediting correctness-first fundamentals catching up on speed, the Oracle acquisition and MariaDB split, and JSONB indexing answering MongoDB. (r/PostgreSQL · 152 pts, 273 comments)
  • What database design decision did you regret later? — Top war stories: is_deleted flags becoming a correctness tax on every query, hand-rolled "transactions" because real ones seemed slow, and outgrown int primary keys. (r/Database · 132 pts, 110 comments)

Wider DBMS & distributed data

  • Please implement a quorum database — An HPTS'26 talk arguing leaderless quorum replication is viable again: why Riak, Voldemort, Megastore and early InfluxDB faded, and which newer leaderless algorithms change the trade-off. (Alex Miller · transactional.blog)
  • Building a serverless ClickHouse — Compute/storage separation for open-source ClickHouse on plain_rewritable S3 disks, with a C++ router linked against ClickHouse's own parser to send reads and writes to on-demand servers. (Jordi Villar · jordivillar.com)
  • rqlite 10.6.1 to 10.7.1 — 10.6.4 fixes a Raft-port flaw that streamed a database backup to unauthorised peers, and 10.6.3 blocks ATTACH for read-only users. 10.7.0 stops forwarded-write retries from duplicating data and moves to SQLite 3.54.1. (Philip O'Toole · philipotoole.com) [release]

Commercial engines (SQL Server, Oracle, MySQL, …)

  • Aurora MySQL error 63955: virtual index ID overflow — Index DDL consumes Aurora-only virtual-index IDs that cannot be reset; at 4,294,967,295, new indexes on virtual columns fail until a dump and restore into a new cluster. (Kartik Saini · aws.amazon.com)
  • Giving the optimizer a hint: MariaDB Server 13.0 — MySQL-syntax hints plus two extras: hints inside view definitions, and TiDB-inspired path-addressed query blocks that reach into views, derived tables and CTEs. (Oleg Smirnov · mariadb.org) [by implementer]
  • TLS connect/disconnect speed-up with WolfSSL — MariaDB's build of bundled WolfSSL never detected __uint128_t, so non-x86 builds used generic bignum code; a two-line check cut 100 TLS connects from 4.50 s to 1.31 s. (Georgi Kodinov · mariadb.org)
  • iClaustron API 1.0, a Rust NDB API for RonDB — An MIT-licensed Rust and C NDB API whose receiver thread only routes messages, supporting key lookups and scans. The author reports 9 M key lookups/s on an M5 Pro laptop at zero allocations per lookup. (Mikael Ronström · mikaelronstrom.blogspot.com) [release] [unverified: self-reported laptop numbers]
  • Reading SQL Server .bak files straight to Parquet — Parsing SQL Server 2025's striped backups with no running instance exported TPC-H SF100 orders (150 M rows) in 10.1 s, against 181 s for DuckDB's mssql extension on the live database. (Romain Ferraton · arpe.io) [vendor benchmark]

Migration experience

  • How we migrate TBs from Heroku without logical replication — Heroku's standard plans expose no WAL, so the migrator uses Bucardo triggers; one oversize btree entry (3,328 > 2,704 bytes) killed a 12-hour copy, so v2 builds secondary indexes afterwards. (Dmitrii Anisovich · planetscale.com) [vendor blog — substantive]
  • Swapping pgvector for turbopuffer — On a shared multi-tenant table, HNSW with hnsw.iterative_scan made small tenants 89× slower at the median (9.1 s vs 103 ms) and changed 7% of results. (modem.ai)
  • An index scan is only half the story — After a parallel-loaded migration to Azure, the same index scan read 101 heap pages instead of 5 for 200 rows; pg_repack --order-by fixed what VACUUM FULL could not. (Richard Yen · richyen.com)

Research & cutting edge

International (non-English sources)

  • A backdoor planted through preload libraries broke an upgrade backup — Attackers with a weak postgres password pointed shared_preload_libraries at a .so in PGDATA; hijacked backends ran a downloader and segfaulted 22,320 times while binary checksums still matched. (岳麓丹枫 · modb.pro) [zh] (orig: PostgreSQL被植入gcmanager-1.so预加载后门致数据库升级备份失败案例分析)
  • GaussDB: equality and LIKE return different rows — A batch-bind insert followed by a swallowed unique violation leaves stale batch-index state, so the next insert never reaches the primary-key index: = finds one row, LIKE two. (DarkAthena · modb.pro) [zh] (orig: 【GaussDB】预警复现:CLD-P-A-2026103 过滤条件等值查询与模糊查询结果不一致问题)
  • From TiDB to PostgreSQL: a production cutover with writes frozen — 171 tables copied in one snapshot and hash-verified before COMMIT; utf8mb4_unicode_ci became a nondeterministic ICU collation, with CHECKs guarding TiDB's PAD SPACE semantics. (hirahara · Zenn) [ja] (orig: TiDB から PostgreSQL へ、本番 DB を書き込みを止めて切り替えた記録)
  • Why I wrote yet another Patroni: PostgreSQL HA in Go with embedded Raft — tembo replaces the external DCS with built-in Raft on bbolt; a primary that loses quorum for 5 s self-fences, well before the 15 s failover deadline. (ckpunT · Habr) [ru] (orig: Зачем я написал ещё один Patroni: PostgreSQL HA на Go со встроенным Raft)
  • An unkillable session caused by plugin_debugger.so — A backend parked at a pldebugger breakpoint blocks in accept() and ignores pg_terminate_backend; attaching and calling pldbg_abort_target lets the terminate land without a restart. (瓶盖吃芥末 · modb.pro) [zh] (orig: PG会话杀不掉问题1:plugin_debugger.so造成的)
  • OceanBase 4.x: a sql_mode mismatch disables a function index — A function index freezes the creating session's sql_mode, so DBeaver's extra STRICT_TRANS_TABLES made the expression non-equivalent: 6.5 s full scan versus 0.138 s with matching sql_mode. (open.oceanbase.com) [zh] (orig: oceanbase v4.x sql_mode不一致导致函数索引失效问题)
  • OceanBase splits INSERT … ON DUPLICATE KEY UPDATE into DELETE + INSERT — Parsed clog shows the update path logged as DELETE plus INSERT by default; a hidden _enable_insertup_direct_update makes it a true UPDATE, which CDC consumers will notice. (瑞蓝创软件 · open.oceanbase.com) [zh] (orig: 关于 OceanBase INSERT ON DUP KEY UPDATE的拆分行为)
  • «ё» is not only for restaurants — On PG 18, unaccent folds both forms of «ё» but is only STABLE, so unusable in an expression index, and russian.stop lists «все» but not «всё». (reddice · Habr) [ru] (orig: На «ё» бывают не только рестораны. Как разработчикам угрожают две буквы)
  • 1040 Too many connections: how one JavaScript loop took down prod — Apache prefork could spawn 8× more workers than MariaDB allowed connections, and logging errors into the same database stretched the outage to four minutes. (Jony2Good · Habr) [ru] (orig: 1040 Too many connections: как один JavaScript-цикл положил прод и почему Laravel-приложение не могло восстановиться)
  • ClickHouse 26.10: range joins without an equality condition — With 10 M fact rows and a 10-row range table, the default ie_join took ~40 s and excluding it 0.15 s; ie_join only wins somewhere between 200 and 500 ranges. (asahide · Qiita) [ja] (orig: ClickHouse 26.10 で等号の無い JOIN を範囲の突き合わせで試してみた)
  • Cloudflare D1 caps LIKE patterns at 50 bytes — D1 lowers SQLite's 50,000-byte LIKE pattern limit to 50 bytes, so a %-wrapped Japanese phrase fails at 17 characters in production while local SQLite tests pass. (hyconsulting · Zenn) [ja] (orig: Cloudflare D1 の LIKE パターンは50バイトまで:日本語の検索が本番だけ失敗する)
  • PostgreSQL disk speed and index experiments — 30 M rows measured on 12 disk/VM paths: the same Apple NVMe full-scanned at 966 MB/s through VMware's virtual SATA but 24 MB/s through its virtual NVMe. (kubo4ka · Qiita) [ja] (orig: PostgreSQLのディスク速度とインデックス実験)

Call for papers

Upcoming events

  • DatomicConf 2026 — Durham, NC, Dec 11 — One-day, single-track conference run by Nubank's Datomic team. Internals picks:
    • How to Fork a Datomic Database (Francis Avila) — cheap clones built from the existing index and log structures, with safe garbage collection; comparable to Postgres branching work.
    • Sketching the Unknown (Paul Rutledge, Dave Gonsalves) — per-attribute theta sketches estimate co-occurrence and drive Datalog clause ordering when the data's shape is unknown.
  • ADC 2026, 37th Australasian Database Conference — Brisbane, Dec 15–17 — CORE-ranked research venue with LNCS proceedings; program and accepted papers not posted yet.

New sources added this week

  • transactional.blog — replication and storage essays and talk transcripts from a FoundationDB-lineage engineer. (Alex Miller)
  • agentml.ai blog — source-level posts on running the ORCA optimizer as a PostgreSQL extension, checked against the stock planner. (Jianghua Yang)
  • xminxmax.dev — Postgres internals tooling: ETW trace probes for Windows builds and an interpreter running inside a live backend. (Bryan Green)
  • jordivillar.com — ClickHouse internals and engineering write-ups. (Jordi Villar)

83 items · yield — mailing lists: ~1,272 messages in window (630 hackers / 230 bugs / 0 performance / 10 general, plus ≥399 pgsql-committers and 3 pgsql-announce) → 48 shortlisted → 20 published (plus 3 releases in the PostgreSQL section) · blogs: ~120 posts in window → 71 shortlisted → 26 published · community: ~212 threads viewed → 21 shortlisted → 2 published (one folded into the CVE-2026-6460 item) · research: 52 cs.DB announcements in window (none Nov 12 or the weekend) → 21 shortlisted → 10 published · international: ru 43→16→3, zh 324→23→5, ja 146→15→4, fr 1→1→0, de 0→0→0 (polyglot search unavailable this run; native feeds, site APIs and the browser used instead).