Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1q9NXv-00062w-5i
	for pgsql-admin@arkaria.postgresql.org; Wed, 14 Jun 2023 10:16:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1q9NXt-0006kO-Pi
	for pgsql-admin@arkaria.postgresql.org; Wed, 14 Jun 2023 10:16:09 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <depesz@depesz.com>)
	id 1q9NXt-0006kE-D8
	for pgsql-admin@lists.postgresql.org; Wed, 14 Jun 2023 10:16:09 +0000
Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com)
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <depesz@depesz.com>)
	id 1q9NXm-0028fE-4x
	for pgsql-admin@lists.postgresql.org; Wed, 14 Jun 2023 10:16:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com;
	s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To:
	Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding:
	Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
	Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:
	List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=zrK5Ux1Ub42wGRWTREFCE5G5QNX0FSYaV1yoTZ4RZG4=; b=UzVSzn0VGFo8GVORU4+cOVMnI1
	58wj76rrVQIJ4GYxxGZ3RoDLWcRcnxJKs4ocIiV9xQEArjDdO6KOSDDGqTOB9d3xZx1WBtk1NtGXw
	odAsIAZOsKAzfFDz3Ow29lVbDS0Zk9tkMPw3MuBqVyqPjE4IHeMxyes8Q1kcHDL2X5po=;
Received: from depesz by depesz.com with local (Exim 4.94.2)
	(envelope-from <depesz@depesz.com>)
	id 1q9NXi-008R7b-Nw; Wed, 14 Jun 2023 12:15:58 +0200
Date: Wed, 14 Jun 2023 12:15:58 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Nikhil Ingale <niks.bgm@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: IS JSON STRICT - In oracle => postgres ??
Message-ID: <ZImTXsqhJPs5urBa@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CALXkTpx66eJKJM1YPFmYJNJwn2LeGAb7qkiXkhyOGBCoKA4isQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CALXkTpx66eJKJM1YPFmYJNJwn2LeGAb7qkiXkhyOGBCoKA4isQ@mail.gmail.com>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/ZImTXsqhJPs5urBa%40depesz.com>
Precedence: bulk

On Wed, Jun 14, 2023 at 03:30:50PM +0530, Nikhil Ingale wrote:
> Hi All,
> In oracle we can use the *is json* check constraint for the json column to
> ensure the data is well formed.
> How do we ensure the same in postgres database?

Well, if the data is in json(b) column, then it is well formed, isn't
it?

Best regards,

depesz