MIME-Version: 1.0
From: veem v <veema0000@gmail.com>
Date: Tue, 15 Jul 2025 01:21:38 +0530
Message-ID: <CAB+=1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67+BMi6Vt1qA@mail.gmail.com>
Subject: Performance of JSON type in postgres
To: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b7be540639e8fd93"
Archived-At: <https://www.postgresql.org/message-id/CAB%2B%3D1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67%2BBMi6Vt1qA%40mail.gmail.com>
Precedence: bulk

--000000000000b7be540639e8fd93
Content-Type: text/plain; charset="UTF-8"

Hi,
It's postgres 15+. And need guidance on JSON types, (for both on premise
vanilla postgres installation and AWS cloud based RDS/aurora postgres
installations).

I have never worked on a JSON data type in the past. But now in one of the
scenarios the team wants to use it and thus want to understand if there are
any pros/cons in using JSONB vs JSON in postgres. Is there a specific
scenario in which one should use one vs other. Any storage or performance
threshold or limitations if any exists etc? Even some team mates suggest
storing it simply in string data types. So I want to understand the
experts' opinion on this which I believe will  be crucial during design
itself.

Regards
Veem

--000000000000b7be540639e8fd93
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br>It&#39;s postgres 15+. And need guidance on JSON ty=
pes, (for both on premise vanilla postgres installation and AWS cloud based=
 RDS/aurora postgres installations). <br><br>I have never worked on a JSON =
data type in the past. But now in one of the scenarios the team wants to us=
e it and thus want to understand if there are any pros/cons in using JSONB =
vs JSON in postgres. Is there a specific scenario in which one should use o=
ne vs other. Any storage or performance threshold or limitations if any exi=
sts etc? Even some team mates suggest storing it simply in string data type=
s. So I want to understand the experts&#39; opinion on this which=C2=A0I be=
lieve=C2=A0will=C2=A0 be crucial=C2=A0during design itself.<div><div><br></=
div><div>Regards</div><div>Veem</div></div></div>

--000000000000b7be540639e8fd93--