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 ) id 1qBWOV-0001xZ-IY for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jun 2023 08:07:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBWOU-0007wI-Cm for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jun 2023 08:07:18 +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 ) id 1qBWOS-0007w6-Ny for pgsql-admin@lists.postgresql.org; Tue, 20 Jun 2023 08:07:18 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qBWON-003Cbn-2v for pgsql-admin@lists.postgresql.org; Tue, 20 Jun 2023 08:07:15 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 412A13200919; Tue, 20 Jun 2023 04:07:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 20 Jun 2023 04:07:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1687248427; x=1687334827; bh=1aiI95K/ds2xOPGZCvC1tolgtV0gpNSGsNQ DvWLxpcc=; b=aT98rzhZX3aJP8XBtFsEaqy7FDlw3QdlR/iE0dTp5praVtYSqiC Ve4mTWgPMjLvLgU85UgyfbR2frn8JBdLbF2MvpiXSwIzmzZ7AToTjefZAAtPJORc ek1al/6okQMQRx0gXpHrHMi1+IvqUCsiCSCzAv+/7ZdTWpLe90kJCAv0PpTHU50W KxKlNWr7Seb3dXTNNk2t9bji4AMAZ/Ny+DBbDOcUPiOA0FKxekSx5NuHkqBSbT86 OuQpGENW3MbxhTbFKim3tkJUeQSVCg9BZD4AJ6jA/tKGkilc32rClnjH/HgmxIiC V/ay2lFYXYCEWEMcfh6ntV5UGtQ8TpqGBSA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1687248427; x= 1687334827; bh=1aiI95K/ds2xOPGZCvC1tolgtV0gpNSGsNQDvWLxpcc=; b=q O7p7vAiMVGx7KJoO0/OJ0foH/vgVBK8IbX1UvWCVtEuYQ3I3JX/CrPybxrzBlPgE o28HXo6pJfTEGcCcTx01Bhu86rR96jnRbTT/x8z6/s1W274u0nuWV+bk8SSRlf1R gae8vUdgnx5pMmMjs092KBS8gPTJcqg8QJxCHVEQd8sDVgUtCAFKZ3Dg6xllmjJ/ Adm7pXVumv9up9bVGDuAGIwa6fS0xzxc0rZuHMslpJB+RVIvN/HXHDUm3kpJw34r +njR17vf3xSAUkvV21Sn5xmWXQN0GfPw3q2nM/qu91sTI6DwYOaIasFegPSTpasQ hObkE9s3d+Cvi/79joa6w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgeefgedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr segvihhsvghnthhrrghuthdrohhrgheqnecuggftrfgrthhtvghrnhepudfgudduhefhje eiueduhfeiffevgefhgffghffgfffgudevhfeljeeijefhudelnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhesvghishgvnhhtrh gruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 20 Jun 2023 04:07:07 -0400 (EDT) Message-ID: <5cd1da78-e1ad-42d2-9f33-9aa0b163293e@eisentraut.org> Date: Tue, 20 Jun 2023 10:07:05 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.2 Subject: Re: IS JSON STRICT - In oracle => postgres ?? To: Nikhil Ingale , pgsql-admin@lists.postgresql.org References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 14.06.23 12:00, Nikhil Ingale wrote: > 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? PostgreSQL 16 has an IS JSON predicate. It doesn't have a STRICT clause, which I don't see in the SQL standard. So it might not do exactly the same thing.