Edition of Saturday 21 November 2026

Squeezing Tables with Postgres 19

Comments on “Squeezing Tables with Postgres 19”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Postgres 19 ships REPACK, which folds VACUUM FULL and CLUSTER into one command and adds a CONCURRENTLY option that compacts tables without blocking reads or writes. Written by Robert Haas, it builds on Antonin Houska's pg_squeeze, using logical decoding of WAL to replay changes made during the copy.

Read the original at enterprisedb.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 22 of 118 with a score of 0.62. The panel rated it highest on technical depth (0.75) and new information (0.72), lowest on audience breadth (0.58). Placed No. 22, No. 42 by score alone: close to “PostgreSQL 19 Released”, No. 9 on Friday 20 November 2026 (−0.001). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Insider engineering write-up on Postgres 19's REPACK CONCURRENTLY, a practical table-compaction feature with technical depth. Well grounded, though somewhat narrative and tied to one database's community.
AI judgeJudge 3gpt-5.6-luna
A detailed first-person engineering account of integrating concurrent table repacking into PostgreSQL 19, including logical decoding, WAL spill handling, tradeoffs, limitations, and testing. It overlaps the PostgreSQL 19 release but adds substantial implementation context.

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.62total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.63
  • Reader interest0.68
  • Audience breadth0.58
  • Practical relevance0.67
  • Substantiated0.65
  • Technical depth0.75
  • New information0.72
  • Counts against: Promotional0.08
  • Counts against: Overclaim0.15

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.620.550.720.630.17+0.24+0.151
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.550.600.880.680.33+0.26+0.176
Audience breadthHow many people who build technology does it concern?0.510.600.620.580.11+0.13+0.075
Practical relevanceHow useful is it to someone who builds software or tech products?0.610.600.780.670.18+0.22+0.146
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.450.650.840.650.39+0.05+0.032
Technical depthHow technically substantive is it?0.760.700.780.750.08+0.05+0.037
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.830.600.720.720.23+0.05+0.036
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.100.100.030.080.07−0.19−0.015
OverclaimDo the headline or conclusions claim more than the body supports?0.230.150.080.150.15−0.11−0.017
Sum of contributions+0.622
Claim-check penalty0.000
Total, as published0.622

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.

Ranked #22 on Rubric, 21 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-21/22/"><img src="https://rubric.hrih.si/badge/2026-11-21/22.svg" alt="Ranked #22 on Rubric, 21 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 1 matches source · 3 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.

  1. Couldn’t checkDate

    In January 2024, Pavel Stehule asked on the Postgres hackers mailing list why there is no VACUUM FULL CONCURRENTLY.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In January 2024, Pavel Stehule asked in the hackers mailing list: why is there no VACUUM FULL CONCURRENTLY”

    The source says

    No passage could be compared.

    Source cited by the article: postgr.es/m/CAFj8pRDK89FtY_yyGw7-MW-zTaHOCY4m6qfLRittdoPocz+dMQ@mail.gmail.com

  2. Matches sourceCausal conclusion

    pg_squeeze, developed by Antonin Houska, uses logical decoding of WAL to apply changes made during the table copy to a transient table, letting applications keep working on the table during compaction.

    The cited source says the same thing.

    The article says

    “when that copy completes, all the changes that occurred during the copy are obtained from WAL by logical decoding, and from there pg_squeeze applies them to that second copy of…”

    The source says

    “we use [logical decoding][4] instead of triggers to capture concurrent changes”

    Source cited by the article: github.com/cybertec-postgresql/pg_squeeze

  3. Couldn’t checkDate

    Antonin Houska proposed reworking VACUUM FULL to host parts of the pg_squeeze code, starting in the Postgres 18 development cycle.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Beginning in the Postgres 18 development cycle, Antonin undertook the task of reworking VACUUM FULL so that it could host (parts of) the pg_squeeze code”

    The source says

    No passage could be compared.

    Source cited by the article: postgr.es/m/82651.1720540558@antos

  4. Couldn’t checkVersion

    The REPACK command, merging VACUUM FULL and CLUSTER under one name, was not committed in Postgres 18 but was committed in Postgres 19, without adding new functionality.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “we couldn't get that in Postgres 18. But we did get it in Postgres 19! This didn't add any new functionality”

    The source says

    No passage could be compared.

    Source cited by the article: postgr.es/c/ac58465e0618

  5. No source givenCausal conclusion

    REPACK (CONCURRENTLY) uses a background worker that decodes WAL and writes changes to a separate spill area on disk, so WAL can be recycled normally regardless of how long REPACK runs.

    The article gives no link or citation for it.

    The article says

    “Antonin added a background worker that decodes WAL and writes the relevant changes to a separate spill area on disk”

    The source says

    No source to compare with.

  6. No source givenVersion

    The Postgres 19 version of REPACK (CONCURRENTLY) omits MVCC safety, snapshot refreshing, and more complicated lock-upgrade handling in the final phase.

    The article gives no link or citation for it.

    The article says

    “we punted on some features, such as MVCC safety, snapshot refreshing, and more complicated handling of the lock upgrade in the final phase”

    The source says

    No source to compare with.

  7. Couldn’t checkGeneralization

    Disaster was declared for Postgres 19, and the feature was at risk of being reverted like other would-be Postgres 19 features.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “disaster was declared for Postgres 19 and it seemed like, as with many other Postgres 19 would-be features, this one would have to be reverted”

    The source says

    No passage could be compared.

    Source cited by the article: rhaas.blogspot.com/2026/10/postgres-19-is-late-and-its-ais-fault.html

  8. No source givenDate

    Postgres 19 was released on the day the article was written, with REPACK as a headline feature.

    The article gives no link or citation for it.

    The article says

    “today Postgres was released and I'm happy that REPACK is a headline feature”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 5 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Squeezing Tables with Postgres 19”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.77

    PostgreSQL 19