| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
| Cc: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Manu Saxena <manu(dot)saxena(at)lavainternational(dot)in> |
| Subject: | Re: Avg/max size of these JSON docs in Postgres |
| Date: | 2021-10-12 17:53:09 |
| Message-ID: | CAHOFxGobn9REnhU0dd=yRvPQ5a_qj97GRr1vxCOdafOfUTjd+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Oct 12, 2021 at 1:43 AM Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
wrote:
> On Tue, 12 Oct 2021 at 08:14, Ram Pratap Maurya
> <ram(dot)maurya(at)lavainternational(dot)in> wrote:
>
> > Confirm what is Avg/max size of these JSON docs in Postgres.
>
> JSON and JSONB datatypes can both be max 1GB in size.
>
That is per row.
Just to confirm- The compression associated with TOAST is only if the value
can fit in line, right? Columns don't get stored out-of-line in a toast
table as a compressed value as I read the documentation. I suppose that
would make reads a bit crazy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-10-12 18:14:46 | Re: Avg/max size of these JSON docs in Postgres |
| Previous Message | Karsten Hilbert | 2021-10-12 17:52:56 | Aw: Re: Fault with initcap |