public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: veem v <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Performance of JSON type in postgres
Date: Mon, 14 Jul 2025 12:54:49 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAB+=1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67+BMi6Vt1qA@mail.gmail.com>
References: <CAB+=1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67+BMi6Vt1qA@mail.gmail.com>

On 7/14/25 12:51, veem v wrote:
> 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.

It is spelled out here:

https://www.postgresql.org/docs/current/datatype-json.html


> 
> Regards
> Veem

-- 
Adrian Klaver
[email protected]

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Performance of JSON type in postgres
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox