DBMS Weekly — 2026-11-02 (week of Nov 2–8)
Days before 19 RC2, Andrew Dunstan reverted the to_json/to_jsonb immutability change after it let JSON expression indexes go stale; anything built on 19rc1 that depends on it must be redefined before dump/restore or pg_upgrade. The 18.7/17.12/16.16/15.20/14.25 notes collect two checkpoint-race fixes, Memoize and Sort wrong results, a pg_trgm GiST fix that needs a REINDEX, and a walsender lost wakeup. AI-found bugs became the list's meta-story, from a tester holding over 1,000 to Peter Geoghegan's LLM-written rival to the nbtree prefix-compression patch. On the blogs failover dominated, alongside UUIDv4's real insert cost, a TOAST page-size trap and PostHog leaving DuckDB.
PostgreSQL
- UUIDv4 vs UUIDv7: what a random primary key costs in Postgres — on 18.6, once the primary key outgrew shared_buffers (~26 M rows), UUIDv4 inserts ran at 0.62–0.69× an ordered key and wrote 1.5–1.9× the WAL per row; generate v7 server-side. (Nikolay Samokhvalov · postgres.ai)
- Postgres logical replication beyond one writer — four regions of pg_auto_failover groups linked only by core logical replication: a planned failover lost nothing,
kill -9gave 2–4 duplicates and no holes, emptiedsynchronized_standby_slotslost 3–13 rows; DDL remains the gap. (Dimitri Fontaine · tapoueh.org)[by pg_auto_failover / pgcopydb author] - Fencing a Postgres primary that might still be alive — promotion alone doesn't stop an old primary that a session can switch to
synchronous_commit = local, so Ubicloud cuts its network (host veth, force-detached AWS NIC, deleted GCP NIC) and promotes anyway if every fence fails. (Furkan Sahin · clickhouse.com / Ubicloud)[vendor blog — substantive] - Designing a reliable unplanned failover — the opposite answer: no lease; Neki fails over only when a reachable replica reports broken replication and none contradicts it, with keepalives and
wal_receiver_timeouttuned so crashes, drops and freezes look alike. (Shlomi Noach · planetscale.com)[vendor blog — substantive] - PostgreSQL document compression: TOAST thresholds, storage policies, and page size — TOAST tries compression only past a hardcoded quarter-page gate that
toast_tuple_targetcan't lower, so on 16/32 KB builds of 19rc1 3.9 KB and 7.7 KB JSONB documents stop compressing. (Franck Pachot · dev.to) - Patroni, Ubuntu 24.04, and two unplanned PostgreSQL failovers — unattended-upgrades updated zlib, needrestart restarted the custom Patroni unit, and with
KillMode=control-groupthe stop signal reached Postgres too: two failovers in a day, traced through journal and dpkg logs. (Franck Pachot · dev.to) - systemd-sysusers and directory-managed Postgres accounts — PGDG RPMs now create
postgresvia sysusers.d at early boot, before AD/LDAP answers, so a directory-managed account gets a local twin with another UID and the cluster fails to start after reboot. (Nick Ivanov · enterprisedb.com) - Establishing the PostgreSQL standard: PGConf.dev 2026 part two — postgres-compat, a reference test for "Postgres-compatible": Postgres's own 200 regression tests and 117 isolation specs run unchanged against the target, plus 74 probes for silent failures and contrib behaviour. (Jimmy Angelakos · vyruss.org)
- Building a table access method, part 7: storing and reading rows —
pg_memtablegains INSERT and a full scan over its DSM arena: how slots carry rows into the AM, what a TID must encode, arena allocation, and visibility with two concurrent writers. (Mats Kindahl · dbmsdrops.kindahl.net) - "server closed the connection unexpectedly" in PostgreSQL — five causes behind libpq's message, each reproduced on 13–18 across six drivers and PgBouncer; no library surfaced the 57P02 crash notice, and an OOM kill logs exactly like
kill -9. (Chris van Eijk · now-next.nl) - A month with WalShadow on ClickHouse Managed Postgres — decoding physical WAL outside Postgres, with no slot, held a 0.37–0.41 s median commit-to-visible latency up to 200,000 rows/s, while logical-replication ClickPipes tracked its 60 s sync interval. (Hidehiko Asahi · clickhouse.com)
[vendor blog][unverified: private preview] - Why I'm maintaining a VectorChord fork and pg_mooncake — VectorChord, silent since April, lives on as
pgsty/*forks for PG 14–18; a pg_mooncake port to pg_duckdb 1.2 went upstream once Mooncake Labs said it would keep maintaining it. (Ruohang Feng · vonng.com) - OrioleDB v1.10.1 and v1.10.2 — releases drop
betaNnumbering a week after the public beta, with no storage or WAL format change. Fixes cover lost updates under REPEATABLE READ, wrong rows through bridged (GIN etc.) indexes, checkpointer and undo-chain PANICs, and decoding crashes on TOASTed tables. Transaction streaming is now disabled at decoding startup cluster-wide. (orioledb · GitHub)[release] - pg_duckdb 1.2.0 — moves to DuckDB 2.0.0 and is explicitly marked experimental, "not ready for production use", over unresolved user reports. Adds initial PostgreSQL 19 support,
INSERT INTO <pg table> SELECT …through DuckDB, and installation into a non-public schema. (duckdb · GitHub)[release] - psqlODBC 18.00.0006 — a security release that "fixes multiple security issues"; the announcement points only to the changelog. (pgsql-announce)
[release][unverified: individual issues not read] - AgensGraph 2.18 — rebased on PostgreSQL 18.6, it adds the first ISO GQL clauses (
LET,FOR,FILTER,NEXT,FINISH) and graph subqueries. Variable-length traversals now use the edge label's index at each hop; a two-hop query that timed out at 20 s takes milliseconds. (pgsql-announce)[release][unverified: self-reported] - pgBadger 13.3 — no longer counts a query twice when both
log_min_duration_statementandauto_explainlog it. Also parses auto_explain's query parameters, fixes multiline statements and--dbuserfiltering, and uses per-run temp files so concurrent runs don't collide. (pgsql-announce)[release] - HypoPG 1.4.5 — fixes relid handling in hypothetical indexes that could crash the backend, and a long-standing thinko in
hypo_estimate_index. (pgsql-announce)[release] - Brume 2.1 — an Apache-2.0 tool that copies a subset of a database for testing with personal data pseudonymised. Format-preserving encryption rewrites primary keys and the foreign keys pointing at them, so referential integrity holds without disabling triggers. (pgsql-announce)
[release]
PostgreSQL mailing lists
- [hackers] PG19 regression in ecd9288624a: JSON_ARRAY() indexes that go stale — the check still accepted
float8[],bytea[]and geometric arrays, whose output functions are IMMUTABLE on REL_19_STABLE, returning 0 rows where a seq scan gave 1; Dunstan reverted it on Nov 6. (Manu, Nikolay Samokhvalov; Andrew Dunstan · pgsql-hackers)[committed: revert] - [hackers] Racing in ROLLBACK PREPARED and checkpoint —
DELAY_CHKPT_STARTnow covers the abort record, so a rolled-back prepared transaction can't return after a crash and be committed, a bug "as old as" 2PC; committed to 14+. (Shihao Zhong; Michael Paquier · pgsql-hackers)[committed] - [hackers] checkpoint can lose a multixact created during its start — the race that could show an old row version next to the new one after a crash is fixed in 14+; the hash-bucket and CLOG siblings are still patches. (Shihao Zhong; Heikki Linnakangas · pgsql-hackers)
[committed] - [hackers] Checkpoints stuck after a failed bulk write inside a savepoint —
smgr_bulk_finish()setsDELAY_CHKPT_STARToutside a critical section, so an ERROR caught by a savepoint leaves it set and every checkpoint waits for the transaction to end. (pgsql-hackers)[open] - [hackers] Preferred way to submit a very large batch of bugs? — pgrust's author reports over 1,000 unreported bugs; Freund asked for deduped, minimised reproducers, and Peter Geoghegan said he holds about 25 AI-found correctness bugs himself. (Michael Malis; Andres Freund, Peter Geoghegan · pgsql-hackers)
[open] - [committers] Memoize: a Param inside a cache-key expression — one of three 14+ wrong-result fixes, with only outer-level Params as keys and the join's input collation; #19853, keys compared with the default
=, is open. (Richard Guo, David Rowley · pgsql-committers)[committed] - [committers] Fix accidental ignoring of subsequent keys in Sort nodes — the single-Datum sort used only the first key, so
count(DISTINCT x COLLATE "C")on a case-insensitive column returned 40 instead of 2 (15+). (David Rowley · pgsql-committers)[committed] - [committers] Hashed SubPlans duplicated in the plan reused a stale hash table — copies of one hashed SubPlan, created by EC constants or OR-qual extraction, never rebuilt after a parameter change and returned stale results; fixed in 14+. (Richard Guo · pgsql-committers)
[committed] - [committers] SQL/JSON ON EMPTY/ON ERROR state leaked from the previous row — results depended on input order;
JSON_VALUE … RETURNING jsonbstuck at NULL and JSON_TABLE PASSING collations were fixed alongside (17+). (Amit Langote · pgsql-committers)[committed] - [committers] NOT IN → anti-join with a coerced sub-select output — the 383eb21eb wrong-results regression from the last two issues is fixed in 19: the inner operand must now be the bare Param. (Richard Guo · pgsql-committers)
[committed] - [hackers] Wrong results with references to JOIN USING aliases — the whole-row reference is built from Vars not marked nullable, so
WHERE x IS NULLis pushed below the outer join (16+); Tom Lane: "should have taken the issue more seriously". (pgsql-hackers)[patch posted] - [committers] Fix possible index corruption in pg_trgm GiST indexes —
gtrgm_unioncould drop the format flag so queries miss rows; the fix in all branches doesn't repair existing indexes, so REINDEX everygist_trgm_opsindex after updating. (Nate Clark; Fujii Masao · pgsql-committers)[committed] - [hackers] GIN pending-list cleanup race — pending entries move into the main tree without a lock, so a half-moved row skips recheck: 2 rows through the index, 1 by seq scan, since 8.4. (Kirill Reshke · pgsql-hackers)
[patch posted] - [hackers] btree_gist on bit/varbit —
gbt_var_union()copies a leaf entry without converting it to internal format, so scans return incomplete results; reindexing will be needed once fixed. (Narek Galstyan · pgsql-hackers)[patch posted] - [hackers] Unlogged bloom indexes break after crash recovery — generic WAL never logged the init-fork metapage; Heikki has a broader fix, and extensions like pgvector's ivfflat log their own init forks. (Narek Galstyan; Heikki Linnakangas · pgsql-hackers)
[patch posted] - [bugs] #19775: incremental backups restored stale visibility-map bits — with checksums and
wal_log_hintsoff, a truncation's VM change escaped the summarizer, so index-only scans after restore could return deleted rows; divergent-timeline prior backups are now rejected (17+). (Fujii Masao · pgsql-bugs)[committed] - [bugs] Lost walsender wakeup stalls synchronous commits — WAL flushed between the check and
WalSndWait()went unnoticed, stalling synchronous commits up towal_receiver_status_interval(10 s); fixed in 16+. (Alex Speller; Fujii Masao · pgsql-bugs)[committed] - [hackers] Lost FOR KEY SHARE lock —
heap_update()releases the buffer lock between computing and writing xmax, silently dropping a KEY SHARE lock taken in between; there's an isolation test but no fix — Heikki "ran out of energy". (Heikki Linnakangas · pgsql-hackers)[open] - [committers] Don't free a cached RI plan that may be in use — last issue's
RI_Fkey_cascade_delsegfault: an invalidation during a nested RI trigger freed the SPI plan still executing; fixed in 14+. (Amit Langote · pgsql-committers)[committed] - [hackers] Emptying oauth_validator_libraries doesn't stop OAuth logins — a reload with an empty list failed and left the old
oauthHBA lines active; fixed in 18+ by rechecking the validator at authentication. (Zsolt Parragi; Daniel Gustafsson · pgsql-hackers)[committed] - [bugs] FORCE ROW LEVEL SECURITY makes ADD/VALIDATE FOREIGN KEY skip rows hidden from the owner —
RI_Initial_Check()still applies the owner's policies, so rows the owner can't see are never checked and the constraint is marked valid (14 to master). (Ludwig Kannicht · pgsql-bugs)[patch posted] - [bugs] set_config('search_path') does not truncate names over 63 bytes — not a bug, but search_path became
GUC_REPORTin 18 and libpq rejects a ParameterStatus over ~30 kB, so a long role-level search_path can lock the role out. (Manav Kumar; Daniel Gustafsson · pgsql-bugs)[patch posted] - [hackers] Partitioned index marked valid while a partition is pending detach — after a cancelled
DETACH PARTITION CONCURRENTLY, CREATE UNIQUE INDEX marks the parent valid with no index on that partition, which then accepts duplicates. (Shihao Zhong; Álvaro Herrera · pgsql-hackers)[patch posted] - [hackers] BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE — 19's new flag lets the postmaster kill such a worker and then forget it, ignoring
bgw_restart_time, even when the command fails. (Zsolt Parragi; Michael Paquier · pgsql-hackers)[patch posted] - [hackers] Commit Sequence Numbers and Visibility — Jeff Davis proposes true CSN order within one durability level but out-of-order visibility across
synchronous_commitlevels, so later snapshots stay supersets and nobody waits. (Jeff Davis · pgsql-hackers)[open] - [hackers] nbtree: opt-in leaf key prefix compression — Peter Geoghegan posted his own April "vibe-coded" prototype against Greg Burd's v8 and asked to settle the on-disk architecture first, since the format must be supported forever. (Greg Burd; Peter Geoghegan · pgsql-hackers)
[patch posted] - [hackers] Fix cumulative WAL statistics double-counting from parallel workers — Fittl wants a back-patched "FromWorkers" counter, Paquier calls that an abuse of
pgWalUsage, and Freund doubts worker WAL belongs to the leader's statement at all. (Lukas Fittl; Michael Paquier, Andres Freund · pgsql-hackers)[open] - [committers] Parallel vacuum now shares one cost budget — each process's delay scales with the number of active workers; 19 and master only, since back-patching would slow parallel VACUUM after a minor update. (Masahiko Sawada · pgsql-committers)
[committed] - [hackers] Draft back-branch release notes are up — "a good bit longer than average"; the notes landed Nov 8, after a COPY ON_ERROR use-after-free fix was committed and reverted the same day. (Tom Lane · pgsql-hackers)
- [hackers] Design proposal: grain — an index AM keeping exact count/sum/min/max per time bucket, plus a new AM callback; on 119 M taxi rows a 365-day total fell from 2,732 ms to 0.5 ms. (pgsql-hackers)
[patch posted][unverified: self-reported] - [hackers] O(N³) planning in choose_plan_name() — 19's subplan naming for plan advice made a 4,000-arm UNION plan in 16.6 s; v6 hashes names above 32 and takes 22 ms. (Robert Haas · pgsql-hackers)
[patch posted] - [hackers] PoC: true in-place major version upgrades — John Naylor answers Haas with versioned catalog objects (release N+1 reads v1 NOT NULL constraints but creates v2); Nathan Bossart expects "a huge amount of complexity". (John Naylor; Nathan Bossart · pgsql-hackers)
[open]
CommitFest (open: PG20-4, #63 · in progress: PG20-3, #62)
- Balance (Nov 2–8): 37 new · 17 closed (13 committed / 4 withdrawn) → net +20 (vs +44 last week; complete counts). Every new entry went to PG20-4; 19 promotions to Ready for Committer. Active at scan: PG20-3 565 (395 needs review / 50 waiting on author / 120 ready for committer), PG20-4 37.
- New this week: Periodically refresh database frozen IDs during autovacuum (Jingtang Zhang) —
datfrozenxidadvances only after a worker finishes its whole table list, so with 600,000+ tables it stays stale; v2, after Andres Freund's same-day review, refreshes it between tables and in manual VACUUM. Also Fix ReadStream handling when heap rescan strategy changes (#7579), Improve row mark handling in self-join elimination (#7598), MERGE loses UPDATE transition rows when moving rows between partitions (#7597), Add pg_stat_progress overview view (#7608). - Closed: committed Fix missing tts_tid in ExecForceStoreHeapTuple (#7371), Teach pg_upgrade to deal with invalid databases (#7262), Fix pg_trgm GiST union (#7385), Fix reuse of stale hashed SubPlan tables (#7384), Avoid resetting subscription two_phase state (#7576, filed and committed the same week) and 8 more; withdrawn #7528, #7584, #7585 and a duplicate.
Community pulse
- A session-level advisory lock that quietly expires with
idle_in_transaction_session_timeout— a driver's implicit transaction left the lock-holding session idle until the timeout killed it; the replies: any failover does the same, so a lock holder must detect losing its session. (r/PostgreSQL · 11 comments) - CTE vs temp table: where SQL Server's estimates fall apart — SQL Server inlines CTEs into one plan while a temp table gets fresh statistics (~7 M vs ~3 k function calls); the consensus: split where estimated and actual rows diverge. (r/SQL · 53 pts, 42 comments)
Wider DBMS & distributed data
- Next-level benchmarking overfitting — GenDB-V's 22–61× over Umbra comes from per-query structures precomputed at load time and dbgen's key layout hardcoded, while Umbra runs all 22 SF10 queries in ~540 ms. (Thomas Neumann · databasearchitects.blogspot.com)
- How Valkey 9.0 reduces the large-object noisy-neighbor problem — 10 MB values are no longer copied into reply buffers; a 16-byte reference plus
writev()on I/O threads cut neighbouring 1 KB GETs' p99.9 from 26.2 ms to 3.10 ms. (Khawaja Shams · valkey.io) - Can you even fsync correctly — the write path from
fprintfdown to NVMe FLUSH/FUA, ending in rules: fsync the parent directory after create or rename, and never retry a failed fsync, because the pages are already clean. (deferworks.org) - Five months treating bugs like patients and coding agents like a medical team — agents added IBM Db2 as a MOLT migration source in under two days for $4,172 in tokens; Oracle support took 9 months and ~$160k in 2024. (cockroachlabs.com)
[vendor blog][unverified: self-reported costs] - Apache DataFusion Comet 1.2.0 — five weeks and 399 commits spent mostly on matching Spark semantics: timestamp timezone labels, −0.0/NaN rules in hashing, min/max and sort keys, collation fallbacks. Adds opt-in native Iceberg v3 writes and an experimental native Delta scan. (Apache DataFusion PMC · datafusion.apache.org)
[release] - CockroachDB 26.4 — skip-level upgrades between yearly .4 releases are GA. Transactional-mode logical data replication applies multi-statement transactions atomically across two data centers and sends failures to a dead-letter queue; online restore serves reads while restoring (preview). (cockroachlabs.com)
[release][vendor blog]
Commercial engines (SQL Server, Oracle, MySQL, …)
- AWS contributes a large-transaction binary log optimization to MySQL — instead of copying a big transaction's spill file into the binlog under a global lock (~7 minutes for 50 GiB), the file becomes the next binlog; proposed upstream on Oct 29. (Xueting Wu, Omar Farhat · aws.amazon.com)
[vendor blog — substantive] - MariaDB performance claim: technically correct, but misleading — last issue's "about 3× faster" 11.8 fix is ~9% above 10.4's pre-regression 52,410 QPS; the 3× is measured against the regression itself. (Jean-François Gagné · jfg-mysql.blogspot.com)
- An alternative to sharding a MongoDB replica set that outgrew its memory — a proxy sends queries to a small fast tier only when it can prove the tier holds the whole answer: 1.6–5.2× throughput, but worse update p99 (455 vs 104–189 ms). (Zelmar Michelini · percona.com)
[vendor blog — substantive][unverified: self-reported PoC]
Migration experience
- Why we're moving our warehouse product off DuckDB — five months after leaving ClickHouse for DuckDB, PostHog leaves again: at ~2 PB, DuckLake's catalog made single-table writes take over 3 minutes, so it moves to a Trino fork and its own table format. (Benjamin Knofe-Vider · posthog.com; HN 187 pts, 119 comments)
Research & cutting edge
- Correctness firewalls for synthesized database components — agent-written engine parts go behind boundaries that may change speed but never results: advisory for cardinality, guarded for search, certified for compression; synthesized search beat learned indexes up to 3×. (Amiri, Binnig, Kipf, Kraska, Marcus et al.) [paper]
- GenDB-V: AI-generated and formally verified database engines — per-query code ships with proofs against a fixed SQL semantics and runs 22–61× faster than DuckDB and Umbra, while a test-only LLM baseline was wrong on 16 of 28 templates. (Lao, Trummer) [paper]
[unverified: template-specialised speedups] - When is one query per template enough? Moving a learned cost model to new hardware — on PostgreSQL in six environments, serial and parallel lines plus one measured query per template reach median Q-error 1.10 (TPC-H) and 1.19 (TPC-DS), near full retraining. (Patel) [paper]
- Fidelity synopses: choosing an ANN index configuration per query — landmark cells record which index configuration met the recall target on sample queries, so the optimizer picks the cheapest one per query in 21–32 µs; median cost 0.72× of static. (Ramanatha, Singh, Ramanath) [paper]
- PQR-Search: per-query recall guarantees for ANN in dynamic vector databases — indexes tuned to 0.99 average recall left 5–19% of queries below it; a random rotation inside IVF gives per-query guarantees that survive updates, at 2.5× HNSW latency. (Loh, Lee) [paper]
- Eliminating servers in state machine replication — both the total order and the materialised state live on disaggregated storage, with clients sharing one state copy through the log; the AirDB KV store cold-starts 10–45× faster than etcd. (Park, Hu, Yu, Balakrishnan, Park) [paper]
- Quirinus: when deterministic concurrency control beats 2PL and OCC for geo-replication — an analytical model of when ordering a batch before execution pays off, then a DCC system reaching up to 6.2× Tiga's TPC-C throughput. (Mao, Zhang, Zhang, Jacobsen) [paper]
[unverified: single configuration] - Recast: storage-resident ANN that handles deletes — raw vectors stay on disk and an uncertainty-bounded quantised IVF stays in memory, fetching only candidates that need refinement; batched updates run 3.1–37× faster than SPFresh and OdinANN. (Yang, Tao, Dong, Chen) [paper]
- USDB: ByteDance's sequence storage for recommender systems — an LSM with time-staged compaction that materialises per-application histories; production migration cut mean write latency 85.8% and infrastructure cost 42.1%. (Zhu, Cai, Yu, … Chai) [paper]
[unverified: production self-report] - Withdrawn: "Teach Your DBMS to LIKE Strings" — the TUM Aho-Corasick wildcard-join paper (up to 30.6× over DuckDB) was withdrawn on Nov 2: "The invariant in this manuscript is wrong." (Nguyen, Ginter, Nguyen, Neumann, Leis) [paper]
International (non-English sources)
- A 1C month-close went from 12 minutes to 8 hours after leaving SQL Server — the culprit was hash-join bucket estimation: COALESCE join keys have no statistics, and the planner takes the smallest per-clause bucket fraction; stock Postgres needs an index covering every join column. (alex7six · Tantor on Habr) [ru]
[vendor blog — substantive](orig: Регистр бухгалтерии, итоги и боль закрытия месяца: разбор кейса оптимизации) - Three storage-integrity incidents, each repaired by what the object can be rebuilt from — a broken
pg_statisticTOAST value, an all-zero B-tree page, and a lost TOAST chunk thatREPLICA IDENTITY FULLkept from being fixed by setting NULL. (瓶盖吃芥末 · modb.pro) [zh] (orig: PostgreSQL 三类存储完整性故障:TOAST 缺块、B-tree 零页与业务字段恢复) - Why one reconciliation query returns a different count every run —
HAVING sum(amount) <> 0overdouble precisionfound 19,596 accounts serially and a different ~17,800 each parallel run, because partial aggregation reorders the additions. (badcasedaily1 · OTUS on Habr) [ru] (orig: Три места, где Postgres отдаёт разные цифры на один и тот же отчёт) - pg_walex, an offline WAL→SQL / undo-SQL extractor, tested on PolarDB 15 — rebuilds the catalog from WAL without connecting; it auto-detected 1 GB segments and produced correct undo even at
wal_level=replica, thanks to full-page images. (岳麓丹枫 · modb.pro) [zh] (orig: pg_walex —— WAL 解析为 SQL / undo SQL 工具使用经验) - postgres_fdw from 27 minutes to 1 second —
ANALYZEon foreign tables took a join from 1,622 s to 2.2 s andfetch_size10,000 to 1.0 s; enum filters aren't shipped, so use= ANY(array(subquery)). (伊藤 寿浩 · FORCIA on Zenn) [ja] (orig: データ連携をボトルネックにさせないためのpostgres_fdwチューニング) - Supabase's transaction-mode pooler carries
SETinto the next client — session-levelset_configleaked to the next client 8 of 8 times, exposing rows an RLS policy meant to hide;set_config(…, true)never leaked. (tomozilla · Qiita) [ja] (orig: Supabaseの接続数は「掛け算」:満杯になると何から止まるか、上限の先まで試した) - MySQL drops loose index scan as soon as
INhas two or more placeholders — 2 ms with literals, 1.6 s with bound parameters from Laravel, on both 8.0.46 and 9.2; emulated prepares restore the fast plan. (DanielSpravtsev · Habr) [ru] (orig: Один запрос: 4 мс с литералами и 3 секунды из Laravel. Как плейсхолдеры в IN выключают loose index scan в MySQL) - Why fallback replication from GreatSQL 8.0 to MySQL 5.7 stopped on collation #255 — a routine's binlog events carry its definition-time
character_set_client, so recreate routines under a collation 5.7 knows. (GreatSQL community · modb.pro) [zh] (orig: GreatSQL 8.0回流MySQL 5.7主从复制中断分析排查过程) - DuckDB's parallel executor read against the morsel-driven paper and its pipeline splitting — plans carry no degree of parallelism, only thread pinning survives of the paper's NUMA design, and pipelines split at sink operators, acyclic by construction. (杨泽 / 勉仁 · Alibaba 数据库内核月报) [zh] (orig: 从 Volcano 到 Morsel:DuckDB 并行执行器的设计原理 / 树怎么变成一组流水线:DuckDB 的 Pipeline 切分)
- Inside Oracle 7.2–9.2
WRAP— pre-10g wrapping stores the PL/SQL front end's DIANA tree with names in a plain lexicon, so V1 wrapped units can be reversed; the format was mapped from 332 reference units. (softwind · Habr) [ru] (orig: Wrap PL/SQL в Oracle 7.2–9.2: DIANA, слои преобразования и формат V1) - Snowflake's classic clustering looked at only the first 5 bytes of a key — that is 1.3 Japanese characters, so
東京都…prefix filters pruned to every Tokyo partition; Optima Clustering's 1 KB keys prune to one. (indigo13love · Snowflake Japan on Zenn) [ja] (orig: Snowflake: Optima Clustering による 1KB クラスタリングキーでの日本語フィルタの改善) - A MySQL collation let
séc_allowslip past asec_deny-list — the accented key matched underutf8mb4_0900_ai_ci, evenutf8mb4_binignores trailing spaces, and onlyutf8mb4_0900_binkept all six variants distinct. (Container CMS team · Zenn) [ja] (orig: MySQL の照合順序で、設定キーの拒否を「séc」の1文字ですり抜けられた)_ - Masking unique columns without duplicate checks — random replacement collides like a birthday problem (~500 pairs per 1 M rows); an 8-round AES Feistel permutation with cycle-walking keeps uniqueness and format without lookups. (shroud_tdm · Habr) [ru] (orig: Маскирование без дублей: перестановка вместо проверок на уникальность)
New sources added this week
- Jean-François Gagné's MySQL blog — long-running MySQL replication/InnoDB blog that checks vendor benchmark framing against the numbers. (Jean-François Gagné)
- PostHog engineering blog — first-hand warehouse-architecture reversals with production numbers. (PostHog)
- Azure SQL dev blog — its "Under the Hood" series recaps the papers behind SQL Server features (recaps, so judged per post). (Microsoft)
- FORCIA Tech Blog [ja] — reproducible database tuning write-ups from production. (FORCIA)
- GreatSQL community [zh] — MySQL-fork replication and binlog case studies from production tickets, syndicated to modb.pro. (GreatSQL)
86 items · yield — mailing lists: 1,204 messages in window (703 hackers / 157 bugs / 0 performance / 23 general, plus 311 pgsql-committers and 10 pgsql-announce) → 79 shortlisted → 38 published (plus 5 releases from pgsql-announce) · blogs: ~115 posts in window → 59 shortlisted → 24 published · community: ~260 threads viewed → 32 shortlisted → 3 published (one folded into the Migration item) · research: 60 cs.DB announcements in window (none on the weekend) → 18 shortlisted → 10 published · international: ru 28→18→5, zh ~305→34→4, ja ~110→17→4, fr 1→1→0, de 0→0→0 (polyglot search unavailable this run; native feeds, site APIs and the browser used instead).