Re: jsonb format is pessimal for toast compression

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org, Larry White <ljw1001(at)gmail(dot)com>
Subject: Re: jsonb format is pessimal for toast compression
Date: 2014-08-09 01:22:22
Message-ID: 53E577CE.5060206@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 08/08/2014 08:45 PM, Tom Lane wrote:
>> Perhaps another options would be a new storage type which basically says
>> "just compress it, no matter what"? We'd be able to make that the
>> default for jsonb columns too, no?
> Meh. We could do that, but it would still require adding arguments to
> toast_compress_datum() that aren't there now. In any case, this is a
> band-aid solution; and as Josh notes, once we ship 9.4 we are going to
> be stuck with jsonb's on-disk representation pretty much forever.
>

Yeah, and almost any other solution is likely to mean non-jsonb users
potentially paying a penalty for fixing this for jsonb. So if we can
adjust the jsonb layout to fix this problem I think we should do so.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-08-09 01:23:29 Re: jsonb format is pessimal for toast compression
Previous Message Tom Lane 2014-08-09 00:45:20 Re: jsonb format is pessimal for toast compression