| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Jan Wieck <jan(at)wi3ck(dot)info> |
| Subject: | Re: jsonb format is pessimal for toast compression |
| Date: | 2014-09-16 19:09:57 |
| Message-ID: | CAGTBQpbqeJoL4EgC59W=akkfJkaejM8s8zgk6u7ynsTXKueAHw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 16, 2014 at 3:12 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> I'll leave it up to the jury to decide if we care or not. It seems like a
> fairly unusual use case, where you push around large enough arrays or
> objects to notice. Then again, I'm sure *someone* will do it. People do
> strange things, and they find ways to abuse the features that the original
> developers didn't think of.
Again, it's not abusing of the feature. It's using it. Jsonb is
supposed to be fast for this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-09-16 19:20:11 | Re: jsonb format is pessimal for toast compression |
| Previous Message | Michael Paquier | 2014-09-16 18:39:44 | Re: [HACKERS] Need guidance to startup |