Re: Very Limited Toast Compression on JSONB (9.4 beta 2)

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Larry White <ljw1001(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Very Limited Toast Compression on JSONB (9.4 beta 2)
Date: 2014-08-01 03:51:47
Message-ID: 53DB0ED3.9070008@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/31/2014 01:44 PM, Larry White wrote:
> Hi,
>
> I'm running an experiment on 9.4 beta 2.
>
> I put 275,000 identical JSON files into a table using JSONB (one per
> row). Each raw text file is 251K in size, so the total uncompressed is
> 69GB. The column storage is set to EXTENDED. There are other toastable
> columns in the table, but none have more than 36 bytes of data in them.
>
> My Toast table is 66GB. I would have expected to get that much (or more)
> compression just from JSONB being a binary format.
>
> If I compress one of these JSON files outside of Postgres, it goes from
> 251K to 1K. So each file should theoretically fit on a single row in the
> toast table. In total, the amount well under a GB when compressed
> outside of PG.
>
> Any guesses as to why there is so little compression of this data or how
> I might remedy the situation?

Are you sure the column storage is EXTENDED and not EXTERNAL?

>
> Thanks much for your help.
>
>
> Larry
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Larry White 2014-08-01 04:42:22 Re: Very Limited Toast Compression on JSONB (9.4 beta 2)
Previous Message Michael Paquier 2014-08-01 01:48:34 Re: Is it possible to create an index without keeping the indexed data in a column?