DigitalOcean, this is not how you launch an "Advanced" Postgres database
Comments on “DigitalOcean, this is not how you launch an "Advanced" Postgres database”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
An independent pgbench comparison by the blogger behind smokentar.com found DigitalOcean's new "Advanced" managed Postgres tier slower than the Standard tier it replaces. At 32 vCPU, writes reached 6.9k TPS versus 26.5k, and p99 write latency was 35.9 ms versus 6.7 ms. Startup averaged 16 minutes versus 3. The author suspects the mandatory PgBouncer pooler is the bottleneck, though this is inferred, not confirmed. The results are one person's tests in one region, and DigitalOcean's own claims were not verified. Standard stops being deployable above 2 vCPU on November 30.
Why it ranked
No. 10 of 142 with a score of 0.69. The panel rated it highest on new information (0.93) and technical depth (0.91), lowest on audience breadth (0.49). The judges disagreed most on overclaim (spread 0.42), so the story is marked contested. Placed No. 10, No. 19 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, reproducible benchmarks of a managed Postgres product launch showing regressions versus claims; strong evidence, high practical relevance for database operators, moderate significance and audience.
- AI judgeJudge 3gpt-5.6-luna
- Extensive, reproducible PostgreSQL service benchmarks expose a consequential managed-database regression and provide actionable infrastructure evidence. Confidence is reduced by single-customer testing, uncertain root-cause inference, and rhetorically stronger conclusions than the evidence strictly proves.
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.69total under rubric v2.3Contestedjudges differ by 0.42 on overclaim
- Significance0.58
- Reader interest0.84
- Audience breadth0.49
- Practical relevance0.81
- Substantiated0.88
- Technical depth0.91
- New information0.93
- Counts against: Promotional0.06
- Counts against: Overclaim0.38
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.58 | 0.45 | 0.72 | 0.58 | 0.27 | +0.24 | +0.140 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.74 | 0.85 | 0.94 | 0.84 | 0.20 | +0.26 | +0.219 |
| Audience breadthHow many people who build technology does it concern? | 0.38 | 0.55 | 0.55 | 0.49 | 0.17 | +0.13 | +0.064 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.77 | 0.80 | 0.86 | 0.81 | 0.09 | +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.95 | 0.85 | 0.84 | 0.88 | 0.11 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 1.00 | 0.85 | 0.88 | 0.91 | 0.15 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.90 | 0.98 | 0.93 | 0.08 | +0.05 | +0.047 |
| 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.11 | 0.05 | 0.01 | 0.06 | 0.10 | −0.19 | −0.011 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.32 | 0.20 | 0.62 | 0.38 | 0.42 , above the contested threshold | −0.11 | −0.042 |
| Sum of contributions | +0.685 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.685 | ||||||
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-18/10/"><img src="https://rubric.hrih.si/badge/2026-11-18/10.svg" alt="Ranked #10 on Rubric, 18 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 4 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkNumber
DigitalOcean's launch blog post claims its Advanced Postgres delivers up to 38% higher throughput alongside a 50% reduction in p99 latency.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “delivering up to 38% higher throughput alongside a 50% reduction in p99 latency”
The source says No passage could be compared.
Source cited by the article: digitalocean.com/blog/introducing-mysql-postgresql-advanced
Couldn’t checkCausal conclusion
DigitalOcean's benchmark fine print says the p99 latency improvement applies only during a failover.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “their benchmark says that it only applies during a failover”
The source says No passage could be compared.
Source cited by the article: web.archive.org/web/20260923173330/https://www.digitalocean.com/cdn-cgi/image/quality=75/https://www.digitalocean.com/api/static-content/v1/images
Matches sourceDate
On November 30 the Standard equivalent of 4-32 vCPU Postgres databases will no longer be deployable on DigitalOcean, leaving the more expensive Advanced as the only option.
The cited source says the same thing.
The article says “on November 30 the Standard equivalent of 4-32 vCPU will no longer be deployable”
The source says “From October 15, new DigitalOcean accounts can no longer create Standard Edition PostgreSQL or MySQL clusters above 4 GiB of RAM or with standby nodes, and from November 30 the…”
Source cited by the article: privatedevops.com/news/digitalocean-database-plan-changes-october-15
Couldn’t checkQuote
DigitalOcean claims Advanced fails over in seconds while Standard fails over in minutes.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “DigitalOcean claims that Advanced fails over in seconds while Standard fails over in minutes”
The source says No passage could be compared.
Source cited by the article: digitalocean.com/api/static-content/v1/images
No source givenBenchmark result
In the author's pgbench tests, Advanced Postgres supported about 70% fewer write transactions per second than Standard out of the box, topping out at 6,891 vs 26,489 TPS at 32 vCPU.
The article gives no link or citation for it.
The article says “Advanced” supports ~70% fewer write transactions per second than Standard out of the box”
The source says No source to compare with.
No source givenBenchmark result
Advanced had up to 436% higher p99 write latency than Standard (6.7 ms to 35.9 ms at 32 vCPU).
The article gives no link or citation for it.
The article says “up to 436% higher p99 write latency (6.7 ms -> 35.9 ms at 32 vCPU”
The source says No source to compare with.
No source givenNumber
Advanced databases took on average about five times as long to start as Standard (3m 19s vs 16m 06s across 15 regions).
The article gives no link or citation for it.
The article says “5x slower startup times (3m 19s -> 16m 06s, averaged across 15 regions”
The source says No source to compare with.
No source givenCausal conclusion
The built-in PgBouncer connection pooler is the bottleneck limiting Advanced's throughput.
The article gives no link or citation for it.
The article says “I believe the bottleneck is the connection pooler (PgBouncer”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 18 Nov 2026, 05:47 UTC. It played no part in the ranking.