PostgreSQL 19
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
PostgreSQL 19's release notes list REPACK, including a CONCURRENTLY mode that avoids blocking reads and writes, plus the pg_plan_advice extension for steering the planner, parallel autovacuum, and a WAIT command for read-your-writes on standbys. Several defaults change: JIT is off, lz4 replaces pglz for TOAST, and max_locks_per_transaction doubles to 128. RADIUS authentication is removed, and standard_conforming_strings is always on. Upgrades need pg_upgrade, dump/restore or logical replication. Some notes, including the release date and the wraparound-warning and C11 claims, could not be verified.
Why it ranked
No. 4 of 140 with a score of 0.77. The panel rated it highest on new information (0.90) and technical depth (0.89), lowest on significance (0.72).
- AI judgeJudge 2claude-haiku-5-5
- Full release notes of a major open-source database version with many concrete changes and migration incompatibilities; primary source, highly relevant to data engineers and backend builders, though it's a long changelog rather than analysis.
- AI judgeJudge 3gpt-5.6-luna
- A primary, highly technical PostgreSQL major-release document with broad database, operations, replication, performance, compatibility, and security implications. It is actionable for many builders and appears distinct from the listed recent coverage.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.77total under rubric v2.3
- Significance0.72
- Reader interest0.77
- Audience breadth0.75
- Practical relevance0.81
- Substantiated0.87
- Technical depth0.89
- New information0.90
- Counts against: Promotional0.04
- Counts against: Overclaim0.09
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.74 | 0.60 | 0.82 | 0.72 | 0.22 | +0.24 | +0.173 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.56 | 0.80 | 0.96 | 0.77 | 0.40 | +0.26 | +0.201 |
| Audience breadthHow many people who build technology does it concern? | 0.64 | 0.80 | 0.82 | 0.75 | 0.18 | +0.13 | +0.098 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.71 | 0.80 | 0.91 | 0.81 | 0.20 | +0.22 | +0.178 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.74 | 0.90 | 0.98 | 0.87 | 0.24 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.88 | 0.85 | 0.93 | 0.89 | 0.08 | +0.05 | +0.044 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.83 | 0.90 | 0.98 | 0.90 | 0.15 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.07 | 0.03 | 0.01 | 0.04 | 0.06 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.14 | 0.10 | 0.03 | 0.09 | 0.11 | −0.11 | −0.010 |
| Sum of contributions | +0.766 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.766 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-20/4/"><img src="https://rubric.hrih.si/badge/2026-11-20/4.svg" alt="Ranked #4 on Rubric, 20 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 1 no source given · 6 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
PostgreSQL 19 has a release date of 2026-11-19.
The article gives no link or citation for it.
The article says “Release date: 2026-11-19”
The source says No source to compare with.
Matches sourceVersion
PostgreSQL 19 adds a REPACK command that reclaims disk space and reorganizes table contents, and REPACK (CONCURRENTLY) allows repacking without blocking reads and writes.
The cited source says the same thing.
The article says “REPACK (CONCURRENTLY) allows repacking without blocking reads and writes to the table”
The source says “Allow other transactions to use the table while it is being repacked”
Source cited by the article: postgresql.org/docs/19/sql-repack.html
Couldn’t checkNumber
PostgreSQL 19 changes the default of max_locks_per_transaction from 64 to 128.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Change default of max_locks_per_transaction from 64 to 128”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/79534f906
Couldn’t checkCausal conclusion
PostgreSQL 19 disables JIT by default because its cost-based activation was determined to be unreliable.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Previously JIT was enabled by default, and activated based on optimizer costs, but this costing has been determined to be unreliable”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/7f8c88c2b
Couldn’t checkCausal conclusion
PostgreSQL 19 removes RADIUS support, because PostgreSQL only supported RADIUS over UDP, which is described as unfixably insecure.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “PostgreSQL only supported RADIUS over UDP, which is unfixably insecure”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/a1643d40b
Couldn’t checkVersion
PostgreSQL 19 changes the default TOAST compression method from pglz to lz4.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Change the default TOAST compression method from pglz to the more efficient lz4”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/34dfca293
Couldn’t checkNumber
PostgreSQL 19 now warns when transaction ID or multixact wraparound is less than 100 million away, up from a previous 40 million threshold.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Issue warnings when the wraparound of transaction IDs or multixacts is less than 100 million away”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/48f11bfa0
Couldn’t checkVersion
PostgreSQL 19 changes the supported C language version to C11, previously C99.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Change the supported C language version to C11”
The source says No passage could be compared.
Source cited by the article: postgr.es/c/f5e0186f8
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 13 pts, not on front page
Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.