PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released
Comments on “PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
The PostgreSQL project released 18.7, 17.12, 16.16, 15.20 and 14.25, plus 19 RC 2, fixing 52 security vulnerabilities and over 140 bugs, per its own announcement. Version 14 is now end-of-life. Several fixes need follow-up: reindexing GIN, pg_trgm GiST and bpchar B-tree indexes, and taking a new full backup if you use incremental backups. PostgreSQL 19 general availability is planned for November 19. The claims come from the project's notice, and the checker could not independently verify them.
Why it ranked
No. 1 of 137 with a score of 0.78. The panel rated it highest on substantiated (0.92) and new information (0.91), lowest on audience breadth (0.69).
- AI judgeJudge 2claude-haiku-5-5
- Major PostgreSQL release with 52 security fixes, concrete upgrade steps and data-integrity warnings; highly practical for database users, though not a landmark for the wider tech field.
- AI judgeJudge 3gpt-5.6-luna
- A primary database security and maintenance release with 52 vulnerabilities, many arbitrary-code-execution issues, corruption fixes, upgrade guidance, and an EOL notice. It is highly actionable for PostgreSQL operators and developers, though narrower than field-wide news.
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.78total under rubric v2.3
- Significance0.72
- Reader interest0.80
- Audience breadth0.69
- Practical relevance0.86
- Substantiated0.92
- Technical depth0.83
- New information0.91
- Counts against: Promotional0.04
- Counts against: Overclaim0.08
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.73 | 0.72 | 0.72 | 0.72 | 0.01 | +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.66 | 0.88 | 0.86 | 0.80 | 0.22 | +0.26 | +0.208 |
| Audience breadthHow many people who build technology does it concern? | 0.55 | 0.85 | 0.68 | 0.69 | 0.30 | +0.13 | +0.090 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.82 | 0.92 | 0.84 | 0.86 | 0.10 | +0.22 | +0.189 |
| 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.87 | 0.90 | 0.98 | 0.92 | 0.11 | +0.05 | +0.046 |
| Technical depthHow technically substantive is it? | 0.91 | 0.85 | 0.72 | 0.83 | 0.19 | +0.05 | +0.041 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.86 | 0.90 | 0.98 | 0.91 | 0.12 | +0.05 | +0.046 |
| 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.06 | 0.03 | 0.02 | 0.04 | 0.04 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.12 | 0.10 | 0.03 | 0.08 | 0.09 | −0.11 | −0.009 |
| Sum of contributions | +0.777 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.777 | ||||||
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-13/1/"><img src="https://rubric.hrih.si/badge/2026-11-13/1.svg" alt="Ranked #1 on Rubric, 13 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 4 no source given · 4 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 givenNumber
The PostgreSQL update release fixes 52 security vulnerabilities and over 140 bugs reported over the last several months.
The article gives no link or citation for it.
The article says “This release fixes 52 security vulnerabilities and over 140 bugs reported over the last several months”
The source says No source to compare with.
Couldn’t checkDate
This is the final release of PostgreSQL 14, which is now end-of-life and will no longer receive security and bug fixes.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “This is the final release of PostgreSQL 14. PostgreSQL 14 is now end-of-life and will no longer receive security and bug fixes”
The source says No passage could be compared.
Source cited by the article: postgresql.org/support/versioning
Couldn’t checkNumber
CVE-2026-6460, a type confusion after ALTER ... SET DATA TYPE that executes arbitrary code, has a CVSS v3.1 score of 8.8.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Type confusion after ALTER ... SET DATA TYPE executes arbitrary code (CVSS v3.1: 8.8”
The source says No passage could be compared.
Source cited by the article: postgresql.org/support/security/CVE-2026-6460
No source givenCausal conclusion
The release fixes GIN index issues that could cause index corruption, leading queries to miss rows or return unrelated rows.
The article gives no link or citation for it.
The article says “Several fixes for GIN indexes that could lead to index corruption, causing queries to miss rows or to return unrelated rows”
The source says No source to compare with.
No source givenCausal conclusion
Disabling B-tree index deduplication for bpchar columns without a length fixes index-only scans that could return wrong results.
The article gives no link or citation for it.
The article says “Disable B-tree index deduplication for columns declared as bpchar without a length, which could cause index-only scans to return wrong results”
The source says No source to compare with.
No source givenVersion
The release updates time zone data files to tzdata release 2026f.
The article gives no link or citation for it.
The article says “This release also updates time zone data files to tzdata release 2026f”
The source says No source to compare with.
Couldn’t checkDate
The planned general availability date for PostgreSQL 19 is November 19, 2026.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The planned date for the general availability of PostgreSQL 19 is November 19, 2026”
The source says No passage could be compared.
Source cited by the article: postgresql.org/developer/beta
Couldn’t checkCausal conclusion
The fix for CVE-2026-6464 caused psql to reject multiple COPY ... FROM STDIN commands in a single command string.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The fix for CVE-2026-6464 caused psql to reject these”
The source says No passage could be compared.
Source cited by the article: postgresql.org/support/security/CVE-2026-6464
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 109 pts, front page
Recorded for context only, checked 15 Nov 2026, 20:42 UTC. It played no part in the ranking.