Feedback-ID: i76984098:Fastmail
Message-ID: <8efa554c-ba95-43d5-953c-def0d53dca9e@aklaver.com>
Date: Mon, 14 Jul 2025 12:54:49 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Performance of JSON type in postgres
To: veem v <veema0000@gmail.com>,
 pgsql-general <pgsql-general@lists.postgresql.org>
References: <CAB+=1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67+BMi6Vt1qA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAB+=1TU2bi8UkdD94kMizsTrTBUgqbdWKtM4Lq67+BMi6Vt1qA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/8efa554c-ba95-43d5-953c-def0d53dca9e%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com