Re: jsonb format is pessimal for toast compression - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: jsonb format is pessimal for toast compression
Date
Msg-id CAHyXU0ztEmcAUtERhNO1k9N126YYifHDjFP_+N4B8QWNNh=YOw@mail.gmail.com
Whole thread Raw
In response to Re: jsonb format is pessimal for toast compression  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, Aug 14, 2014 at 11:52 AM, Bruce Momjian <bruce@momjian.us> wrote:
> On Thu, Aug 14, 2014 at 12:22:46PM -0400, Tom Lane wrote:
>> Bruce Momjian <bruce@momjian.us> writes:
>> > Uh, can we get compression for actual documents, rather than duplicate
>> > strings?
>>
>> [ shrug... ]  What's your proposed set of "actual documents"?
>> I don't think we have any corpus of JSON docs that are all large
>> enough to need compression.
>>
>> This gets back to the problem of what test case are we going to consider
>> while debating what solution to adopt.
>
> Uh, we just one need one 12k JSON document from somewhere.  Clearly this
> is something we can easily get.

it's trivial to make a large json[b] document:
select length(to_json(array(select row(a.*) from pg_attribute a))::TEXT);

select



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: replication commands and index terms
Next
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)