Edition of Wednesday 11 November 2026

Chris van Eijk: JSON vs. jsonb in PostgreSQL: size and speed, measured

Comments on “Chris van Eijk: JSON vs. jsonb in PostgreSQL: size and speed, measured”

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

Chris van Eijk of Now-Next measured json against jsonb on PostgreSQL 17.11 and 18.6. Table size depends on the documents: a million compact 200-byte documents took 17.8% more space as jsonb, while pretty-printed ones took 3.6% less. Across all cases the range ran from 22.6% smaller to 40.9% larger. Reading one key with ->> was 2.7 to 10.6 times faster from jsonb. Only jsonb supports equality and GIN indexing. The figures come from one machine and the author's own scripts. He could not reproduce a published 26% saving.

Read the original at now-next.nl. 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. 12 of 143 with a score of 0.70. The panel rated it highest on substantiated (0.95) and technical depth (0.94), lowest on significance (0.52). Placed No. 12, No. 19 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, carefully measured PostgreSQL json vs jsonb benchmark with reproducible scripts; highly substantive and practical for data-focused builders, though a niche topic with limited breadth and no tie to recent stories.
AI judgeJudge 3gpt-5.6-luna
A reproducible, detailed PostgreSQL benchmark measures storage, read, indexing, compression, and update tradeoffs across versions and document shapes, with scripts and limitations. It offers actionable guidance for database-backed software, though its scope is specialized.

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

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.52
  • Reader interest0.77
  • Audience breadth0.53
  • Practical relevance0.84
  • Substantiated0.95
  • Technical depth0.94
  • New information0.92
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.13

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.530.350.680.520.33+0.24+0.125
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.700.700.900.770.20+0.26+0.199
Audience breadthHow many people who build technology does it concern?0.530.500.550.530.05+0.13+0.068
Practical relevanceHow useful is it to someone who builds software or tech products?0.900.800.820.840.10+0.22+0.184
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.1.000.900.940.950.10+0.05+0.047
Technical depthHow technically substantive is it?1.000.900.910.940.10+0.05+0.047
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.900.980.920.10+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.030.050.010.030.04−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.190.150.040.130.15−0.11−0.014
Sum of contributions+0.698
Claim-check penalty0.000
Total, as published0.698

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

Claim check

Claim check: 2 matches source · 5 no source given · 1 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 checkNumber

    In a 2015 PGConf.Russia talk by Korotkov, Bartunov and Sigaev, 1.25 million bookmarks took 1,374 MB as jsonb against 1,322 MB as json, an overhead of under 4%.

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

    The article says

    “1.25 million bookmarks take 1,374 MB as jsonb against 1,322 MB as json: “overhead is < 4%”

    The source says

    No passage could be compared.

    Source cited by the article: pgconf.ru/rmedia/2015c/korotkov.pdf

  2. Matches sourceNumber

    A benchmark republished on BestHub in September 2026 reports about 888 MB for jsonb against 1,200 MB for json for a million rows, 26% smaller.

    The cited source says the same thing.

    The article says

    “reports about 888 MB against 1,200 MB for a million rows, 26% smaller”

    The source says

    “Storage size: JSON ~1200 MB, JSONB ~888 MB → JSONB saves 26% (whitespace removal + key deduplication”

    Source cited by the article: besthub.dev/articles/postgresql-json-vs-jsonb-1m-row-benchmark-shows-7x-query-speed-gap-827db964c168

  3. Matches sourceNumber

    PostgreSQL tries to compress a value once a row gets larger than about 2 kB.

    The cited source says the same thing.

    The article says

    “PostgreSQL tries to compress a value once a row gets larger than about 2 kB, according to the documentation on TOAST”

    The source says

    “The TOAST management code is triggered only when a row value to be stored in a table is wider than TOAST_TUPLE_THRESHOLD bytes (normally 2 kB”

    Source cited by the article: postgresql.org/docs/17/storage-toast.html

  4. No source givenNumber

    Running the BestHub generator for a million rows, jsonb came out 6.7% larger than json (653.5 against 612.6 MB).

    The article gives no link or citation for it.

    The article says

    “jsonb came out 6.7% larger, 653.5 against 612.6 MB”

    The source says

    No source to compare with.

  5. No source givenNumber

    Reading one key with ->> was 2.7 to 10.6 times faster from jsonb than from json in every case timed.

    The article gives no link or citation for it.

    The article says

    “Reading one key with ->> was 2.7 to 10.6 times faster from jsonb in every case we timed”

    The source says

    No source to compare with.

  6. No source givenNumber

    A million compact ~200-byte documents took 17.8% more room as jsonb, while the same documents pretty-printed took 3.6% less.

    The article gives no link or citation for it.

    The article says

    “a million compact documents of about 200 bytes took 17.8% more room as jsonb, while the same documents pretty-printed took 3.6% less”

    The source says

    No source to compare with.

  7. No source givenFirst, only or fastest

    Only jsonb can be compared, grouped or indexed for containment; json has no equality operator and no GIN operator class.

    The article gives no link or citation for it.

    The article says

    “only jsonb can be compared, grouped or indexed for containment at all”

    The source says

    No source to compare with.

  8. No source givenCausal conclusion

    Compression is why compact medium documents are 36% larger as jsonb before compression but 16.6% smaller on disk.

    The article gives no link or citation for it.

    The article says

    “That is how a type that is 36% larger before compression ends up 16.6% smaller on disk”

    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 11 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 “Chris van Eijk: JSON vs. jsonb in PostgreSQL: size and speed, measured”

More on Rubric

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