Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1vSh2S-003lUI-1D
	for pgsql-docs@arkaria.postgresql.org;
	Mon, 08 Dec 2025 19:36:52 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1vSh2Q-001NmL-31
	for pgsql-docs@arkaria.postgresql.org;
	Mon, 08 Dec 2025 19:36:51 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vSh2Q-001NmD-2G
	for pgsql-docs@lists.postgresql.org;
	Mon, 08 Dec 2025 19:36:51 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vSh2P-003u3v-0Z
	for pgsql-docs@lists.postgresql.org;
	Mon, 08 Dec 2025 19:36:50 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5B8Jah7w3100802;
	Mon, 8 Dec 2025 14:36:43 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erik Wienhold <ewie@ewie.name>
cc: Bob Kline <bkline@rksystems.com>, pgsql-docs@lists.postgresql.org
Subject: Re: Inclusion of json in list of standard data types
In-reply-to: <31bad2c4-1876-4cfe-9463-08f4b02bf536@ewie.name>
References: 
 <CAGjKmVoP4qVeJgkaBtQ6L46+OLARzmym53uQGhp5COw4wp65yQ@mail.gmail.com>
 <2326014.1765045678@sss.pgh.pa.us>
 <31bad2c4-1876-4cfe-9463-08f4b02bf536@ewie.name>
Comments: In-reply-to Erik Wienhold <ewie@ewie.name>
	message dated "Mon, 08 Dec 2025 19:33:42 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3100800.1765222603.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Mon, 08 Dec 2025 14:36:43 -0500
Message-ID: <3100801.1765222603@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Archived-At: 
 <https://www.postgresql.org/message-id/3100801.1765222603%40sss.pgh.pa.us>
Precedence: bulk

Erik Wienhold <ewie@ewie.name> writes:
> But does Postgres' json type really map to the JSON type defined by
> SQL:2023?  jsonb appears to be closer to that, although I don't have
> access to that particular version of the standard.  Peter wrote [1]
> about the compatibility with SQL:2023 and noted that the standard maps
> more readily to jsonb (see 3rd bullet point in the notes section) and
> features T879–T882 still only apply to jsonb.

Well, there is the weasel wording right at the start of that <note>:

    The following types (or spellings thereof) are specified by SQL:

This note also doesn't get into the rather large semantic gap between
what SQL says TIMESTAMP WITH TIME ZONE is and what timestamptz
actually does.  I think the point of the note is mostly to say that
"you have some hope of interoperability with other DBMSes if you
use these types".

			regards, tom lane