From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: stephen@infowerks.com
Subject: Postgres jsonb data
Date: Tue, 20 May 2025 13:41:30 +0000
Message-ID: <174774849023.1455382.3103677107495562713@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/datatype-json.html
Description:
Documentation suggests that a json type of null doesn't turn into anything
when read into a jsonb, because the json type of null doesn't correspond to
the postgres type of NULL. We've found that in fact it's treated the same
as the string "null" - and the documentation probably should reflect this
edge case.
We're currently using Postgres 14, and it's possible that this has changed
in later versions, but I'm using the Postgres 14 documentation - and this is
table 8.23 in that version of the documentation (formatting doesn't copy
from the webpage into this form):
Table 8.23. JSON Primitive Types and Corresponding PostgreSQL Types
JSON primitive type PostgreSQL type Notes
string text \u0000 is disallowed, as are Unicode escapes representing
characters not available in the database encoding
number numeric NaN and infinity values are disallowed
boolean boolean Only lowercase true and false spellings are accepted
null (none) SQL NULL is a different concept
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, stephen@infowerks.com
Subject: Re: Postgres jsonb data
In-Reply-To: <174774849023.1455382.3103677107495562713@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox