From: | Sean Flaherty <sflaherty(at)grndwork(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Increased storage size of jsonb in pg15 |
Date: | 2023-12-28 20:41:03 |
Message-ID: | CAOscTZP+rsXRF6b2m+v6oahgcsQ8s7ErZS-wiZdD7HA3boH7sA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm rather new to the mailing list, are there any additional steps I should
take (i.e. posting to pgsql-hackers, etc.)?
On Thu, Dec 28, 2023 at 11:23 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 12/28/23 09:13, Sean Flaherty wrote:
> > Follow-up:
> > Working with AWS, we found that starting in RDS Postgres 15, the
> > default_toast_compression parameter is set to use lz4 compression
> > instead of pglz. This resulted in the increased json storage size we
> > were seeing.
> >
> > I have been able to reproduce the increased storage size on RDS Postgres
> > and using my local docker instance of postgres 15.5 by changing the
> > local default_toast_compression value in postgresql.conf.
> >
> > I have attached the test script we use to create a table, insert some
> > test records and a query to test the JSON data size on disk.
>
> I can confirm I see the same results using Postgres 16 installed from
> the PGDG repo on Ubuntu 22.04. That the lz4 data size is greater then
> the pglz data size.
>
> >
> >
> > Kind regards,
> > Sean
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-12-28 20:47:10 | Re: Increased storage size of jsonb in pg15 |
Previous Message | Adrian Klaver | 2023-12-28 18:23:52 | Re: Increased storage size of jsonb in pg15 |