| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Seref Arikan <serefarikan(at)gmail(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: JSONB spaces in text presentation |
| Date: | 2014-09-24 14:34:44 |
| Message-ID: | 5422D684.8040807@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 09/24/2014 07:22 AM, Seref Arikan wrote:
> This is interesting. Most binary encoding methods I use produce smaller
> files than the text files for the same content.
> Having read your mail, I've realized that I have no reason to accept the
> same from the jsonb. I did a quick google search to see if it is wrong
> to expect binary encoding to decrease size and saw that I'm not alone
> (which still does not mean I'm being reasonable).
> This project: http://ubjson.org/#size is one of the hits which mentions
> some nice space gains thanks to binary encoding.
>
> The "much larger" part is a bit scary. Is this documented somewhere?
I believe Merlin is referring to the issue in this thread:
http://www.postgresql.org/message-id/27839.1407467863@sss.pgh.pa.us
>
> Best regards
> Seref
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emanuel Araújo | 2014-09-24 14:39:46 | How to clone CURRENT_DATE to SYSDATE ? |
| Previous Message | Seref Arikan | 2014-09-24 14:22:00 | Re: JSONB spaces in text presentation |