| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Peter Geoghegan <pg(at)heroku(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <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-15 18:51:23 |
| Message-ID: | 53EE56AB.1090303@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/14/2014 07:24 PM, Tom Lane wrote:
> We can certainly reduce that. The question was whether it would be
> worth the effort to try. At this point, with three different test
> data sets having shown clear space savings, I think it is worth
> the effort. I'll poke into it tomorrow or over the weekend, unless
> somebody beats me to it.
Note that I specifically created that data set to be a worst case: many
top-level keys, no nesting, and small values. However, I don't think
it's an unrealistic worst case.
Interestingly, even on the unpatched, 1GB table case, the *index* on the
JSONB is only 60MB. Which shows just how terrific the improvement in
GIN index size/performance is.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-08-15 20:38:06 | Re: jsonb format is pessimal for toast compression |
| Previous Message | Fujii Masao | 2014-08-15 18:40:26 | Re: How about a proper TEMPORARY TABLESPACE? |