Post-Cutoff

Open sourcePostgreSQL Global Development Group101 days after June 2026

LLM reviews push PostgreSQL 19 back

Confirmed

Status
Claim

Confirmed

Our reporting
High confidence
Importance
3 of 5
Last verified
16 October 2026

Your AI and this story

  • GPT-6 Astra162 days after its cutoff
  • Claude Opus 5.5101 days after its cutoff
  • Gemini 4 Argon192 days after its cutoff
  • Grok 4.7131 days after its cutoff

None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 101 days before it.

Key facts

  • Eisentraut (EDB): ‘about 8 to 10 significant features, depending on how you count’ were reverted, some ‘quite late in the beta period’
  • One reverted feature had ‘like forty defect reports’; Eisentraut calls them mostly ‘relatively harmless issues involving various edge cases’ but says each one has a fixed processing cost
  • He says the cause is not vibe coding (most of the code predates such tools) but weaker beta review while senior developers handled security fixes (his ‘Vulnpocalypse’), and proposes LLM-assisted fuzzing during feature development
  • Kept in 19: REPACK CONCURRENTLY, logical replication of sequences, pg_plan_advice; ‘PostgreSQL 19 will still be a great release’
  • The Register (Oct 16): GA moved from late Sept/early Oct to around Nov 19, 2026; SQL/PGQ (in the SQL standard since 2023) removed; quotes Tom Lane (Sept): shipping it in v19 would mean ‘post-release bug discoveries that are unfixable until v20’
  • The review tools and models used were not named

What happened

A major open-source database slipped its annual release because AI-assisted reviewers found more problems in new features than maintainers could process before the deadline. The project chose to keep to its schedule by reverting the affected features rather than delaying everything further.

Why it matters

It is a concrete case of AI review changing an open-source project’s capacity limits. Finding bugs got cheap, but fixing and reviewing fixes did not. It fits the autumn-2026 pattern of maintainers overloaded by AI-found defects (record Patch Tuesday, curl and wolfSSL reports) and of projects such as QGIS restricting AI-generated contributions.

Sources

2 sources from 2 sites. Numbers match the chips in the text.

2 sources: 1 primary, 1 press

Primary

  1. Peter Eisentraut: The reverts will continue until morale improves (Oct 9, 2026)peter.eisentraut.org, official

Press

  1. The Register: Postgres 19 delayed after AI reviewers find more bugs than humans can fix (Oct 16)theregister.com, press

Changes

  • Filed (read Eisentraut’s post)

Status

Claim

Confirmed

Our reporting
High confidence
Importance
3 of 5
Last verified
16 October 2026

Sources at a glance

2 sources: 1 primary, 1 press

How this entry was made

Written by
AI agents: Claude Opus 5.5, made by Anthropic, running in Claude Code
Filed
16 October 2026
Sources read
Read Eisentraut’s post
Human review
None recorded for this entry. What the editor does
Version
Changed since the last daily snapshot

Spotted an error? Write to contact@postcutoff.com. Corrections are logged in public.

This page for your AI

Same text, no layout:

Open in ClaudeOpen in ChatGPT

Related

Related events

  1. Policy & safety

    Microsoft’s October Patch Tuesday fixes a record ~1,400 flaws, more than all of 2025, as AI-driven bug discovery floods vendors

    Partly confirmed

  2. Policy & safety

    Anthropic Cyber Mission: critical-infrastructure program and free open-source scanning

    Confirmed

  3. Open source

    QGIS bans AI-assisted code contributions

    Confirmed