Edition of Wednesday 18 November 2026

Chris van Eijk: invalid input syntax for type JSON in PostgreSQL, measured

Comments on “Chris van Eijk: invalid input syntax for type JSON in PostgreSQL, 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 tested "invalid input syntax for type json" on PostgreSQL 16.15, 17.11 and 18.6. Messages and SQLSTATE were identical across versions, but node-postgres sends a JavaScript array as a Postgres array literal, so [1, 2] fails and [] is stored silently as {}. IS JSON accepts three inputs that jsonb rejects, so use pg_input_is_valid. On 18.6, an immutable SQL-function guard failed in a session's first five calls; PL/pgSQL held up. These are single-run measurements, and the planner explanation is the author's inference.

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. 9 of 142 with a score of 0.70. The panel rated it highest on technical depth (0.96) and substantiated (0.93), lowest on significance (0.53). Placed No. 9, No. 13 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, heavily measured PostgreSQL JSON error analysis across drivers and versions; highly practical and technically deep, though niche in audience and largely a reference-style writeup rather than major news.
AI judgeJudge 3gpt-5.6-luna
A highly reproducible PostgreSQL investigation with extensive measurements, driver comparisons, migration pitfalls, SQLSTATE details, and a PostgreSQL 18 planner regression. It is directly actionable for database and application engineers, though its scope is mainly PostgreSQL users.

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.53
  • Reader interest0.76
  • Audience breadth0.56
  • Practical relevance0.88
  • Substantiated0.93
  • Technical depth0.96
  • New information0.74
  • Counts against: Promotional0.03
  • 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.560.400.620.530.22+0.24+0.126
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.690.700.880.760.19+0.26+0.197
Audience breadthHow many people who build technology does it concern?0.580.600.500.560.10+0.13+0.073
Practical relevanceHow useful is it to someone who builds software or tech products?0.920.850.860.880.07+0.22+0.193
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.990.900.900.930.09+0.05+0.047
Technical depthHow technically substantive is it?1.000.950.940.960.06+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.790.600.830.740.23+0.05+0.037
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.140.200.120.150.08−0.11−0.017
Sum of contributions+0.697
Claim-check penalty0.000
Total, as published0.697

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

Claim check

Claim check: 4 matches source · 2 no source given · 2 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 checkQuote

    The PostgreSQL 18 release notes list the improvement to SQL-language function plan caching under the optimizer section, not under incompatibilities.

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

    The article says

    “Improve SQL-language function plan caching”

    The source says

    No passage could be compared.

    Source cited by the article: postgresql.org/docs/18/release-18.html

  2. Couldn’t checkQuote

    The PostgreSQL 18 commit says the old SQL function plans could not be customized to specific values of the function's parameters.

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

    The article says

    “could not be customized to specific values of the function’s parameters”

    The source says

    No passage could be compared.

    Source cited by the article: postgr.es/c/0dca5d68d

  3. Matches sourceQuote

    The PostgreSQL documentation says function arguments and local variables can be inserted into queries as constants for planning purposes.

    The cited source says the same thing.

    The article says

    “the values of function arguments and local variables can be inserted into queries as constants for planning purposes”

    The source says

    “since the values of function arguments and local variables can be inserted into queries as constants for planning purposes”

    Source cited by the article: postgresql.org/docs/17/sql-expressions.html

  4. Matches sourceQuote

    The PostgreSQL PREPARE documentation says the first five executions are done with custom plans.

    The cited source says the same thing.

    The article says

    “the first five executions are done with custom plans”

    The source says

    “The current rule for this is that the first five executions are done with custom plans and the average estimated cost of those plans is calculated”

    Source cited by the article: postgresql.org/docs/17/sql-prepare.html

  5. Matches sourceQuote

    The PostgreSQL documentation says json checks Unicode escapes only for syntactic correctness, while jsonb rejects \u0000 because it cannot be represented in PostgreSQL's text type.

    The cited source says the same thing.

    The article says

    “rejects \u0000 (because that cannot be represented in PostgreSQL’s text type”

    The source says

    “In the input function for the json type, Unicode escapes are allowed regardless of the database encoding, and are checked only for syntactic correctness”

    Source cited by the article: postgresql.org/docs/17/datatype-json.html

  6. Matches sourceQuote

    The node-postgres documentation says JavaScript arrays are converted to a string describing a Postgres array, and objects get JSON.stringify.

    The cited source says the same thing.

    The article says

    “Converted to a string that describes a Postgres array”

    The source says

    “Converted to a string that describes a Postgres array. Each array item is recursively converted using the rules described here”

    Source cited by the article: node-postgres.com/features/queries

  7. No source givenCausal conclusion

    On PostgreSQL 18.6, an immutable SQL function wrapping the pg_input_is_valid guard failed on invalid values arriving in its first five calls in a session, while 16.15 and 17.11 did not fail.

    The article gives no link or citation for it.

    The article says

    “In a new session it failed when the invalid value came in one of the function’s first five calls, and from the sixth call on it returned NULL”

    The source says

    No source to compare with.

  8. No source givenGeneralization

    IS JSON gave the same answers as pg_input_is_valid(txt, 'json') over all 38 inputs and differed from the jsonb check on three inputs, which a cast to jsonb rejected.

    The article gives no link or citation for it.

    The article says

    “IS JSON called them valid, and a cast to jsonb failed on all three”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 4 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 18 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: invalid input syntax for type JSON in PostgreSQL, measured”

More on Rubric

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

  1. Score 0.77

    PostgreSQL 19