| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-11 20:44:05 |
| Message-ID: | CAM3SWZTVkdKqi+Leu9CgA9VBG7i97=qRGxzsU4DST4SLY8gO8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 11, 2014 at 1:01 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> We've got a clear example of someone, quite reasonably, expecting their
> JSONB object to be compressed using the normal TOAST mechanism, and
> we're failing to do that in cases where it's actually a win to do so.
> That's the focus of this discussion and what needs to be addressed
> before 9.4 goes out.
Sure. I'm not trying to minimize that. We should fix it, certainly.
However, it does bear considering that JSON data, with each document
stored in a row is not an effective target for TOAST compression in
general, even as text.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Singer | 2014-08-11 21:22:27 | Re: 9.4 logical replication - walsender keepalive replies |
| Previous Message | Stephen Frost | 2014-08-11 20:01:24 | Re: jsonb format is pessimal for toast compression |