Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
72 65 79 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
66 54 78 -
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 1 promise resolved, 5 needed for a score.
All types combined: 71 (likely 64 to 77, high confidence), from 79 claims: 60 factual claims, 19 predictions. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Balaji Srinivasan's claims
23 claims
“Postgres indexes it natively these days with JSONB!”
Balaji Srinivasan, writing on X 24 December 2019 Post by @balajis on X, 2019-12-24 (X)
PostgreSQL natively indexes JSON data via the JSONB type.
Resolved true The record shows it happened or was so.
What would count as true or false
True: as of 2019-12-24, released PostgreSQL versions supported indexing jsonb columns with built-in index types (e.g. GIN with jsonb_ops or jsonb_path_ops, or B-tree/expression indexes) and no third-party extension. Mostly true: native jsonb indexing existed but with a minor caveat in how it is described, e.g. it requires an explicit GIN index rather than happening automatically. Mixed or mostly false: indexing jsonb required extensions or worked only in limited ways. False: PostgreSQL had no jsonb type or no native way to index it at that date.
Evidence
- 8.14. JSON Types PostgreSQL Global Development Group (postgresql.org, PostgreSQL 11 documentation)
“The default GIN operator class for jsonb supports queries with top-level key-exists operators ?, ?& and ?| operators and path/value-exists operator @>.”
- 8.14. JSON Types PostgreSQL Global Development Group (postgresql.org, PostgreSQL 11 documentation)
“The non-default GIN operator class jsonb_path_ops supports indexing the @> operator only. An example of creating an index with this operator class is:”
- 8.14. JSON Types PostgreSQL Global Development Group (postgresql.org, PostgreSQL 11 documentation)
“jsonb also supports btree and hash indexes. These are usually useful only if it's important to check equality of complete JSON documents.”
- Release 9.4 PostgreSQL Global Development Group (postgresql.org, release notes) · 18 December 2014
“This new type allows faster access to values within a JSON document, and faster and more useful indexing of JSON columns.”
Reasoning
The PostgreSQL 9.4 release notes, dated 2014-12-18 (E4), introduced the jsonb type and describe "faster and more useful indexing of JSON columns". That was five years before the claim date. The PostgreSQL 11 documentation (E1–E3) describes built-in index support for jsonb: the default GIN operator class, the jsonb_path_ops GIN operator class, and btree and hash indexes. None of these needs a third-party extension. The user has to create these indexes explicitly, but the quote does not say indexing happens automatically, so the claim meets the criteria for true.
Cite this claim
Balaji Srinivasan, “PostgreSQL natively indexes JSON data via the JSONB type.” (said 24 December 2019). Verdict: resolved true. Reliability API, claim c_233f5ba6efa7, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_233f5ba6efa7
Claims without a verdict
- Unresolvable 148
- Not yet due 21
- Own records only 2
- Not researched 227
- Not checkable 1,091
Is a verdict here wrong, or do you speak for Balaji Srinivasan? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.