From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | veem v <veema0000(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Performance of JSON type in postgres |
Date: | 2025-07-14 19:54:49 |
Message-ID: | 8efa554c-ba95-43d5-953c-def0d53dca9e@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2025-07-14 19:56:16 | Re: Syntax error needs explanation |
Previous Message | veem v | 2025-07-14 19:51:38 | Performance of JSON type in postgres |