Re: Design strategy for table with many attributes

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Lok P <loknath(dot)73(at)gmail(dot)com>
Cc: Guyren Howe <guyren(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Design strategy for table with many attributes
Date: 2024-07-05 08:58:35
Message-ID: CAApHDvqK+Ji5syVZoThQvKKAtWt=cO14Mf7NwWwrHbPoPMqWfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 5 Jul 2024 at 20:53, Lok P <loknath(dot)73(at)gmail(dot)com> wrote:
> However out of curiosity, if the roasted/compressed component or column which is JSON itself goes beyond 8k post compression, will it break then?

No. The size limit of a varlena field such as TEXT, JSON or JSONB is
1GB. See "field size" in [1].

Please also read [2].

David

[1] https://www.postgresql.org/docs/current/limits.html
[2] https://www.postgresql.org/docs/current/storage-toast.html

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sud 2024-07-05 09:08:25 Load a csv or a avro?
Previous Message Lok P 2024-07-05 08:53:17 Re: Design strategy for table with many attributes