| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, "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-24 00:51:39 |
| Message-ID: | CAM3SWZTszbGY-Td=AdXM5E3Wp2iuuqj1T3_6mWEVhQHZEXcz1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 19, 2014 at 5:40 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> I think we should bite the bullet and break compatibility with 9.4beta2
> format, even if we go with "my patch". In a jsonb object, it makes sense to
> store all the keys first, like Tom did, because of cache benefits, and the
> future possibility to do smart EXTERNAL access. Also, even if we can make
> the on-disk format compatible, it's weird that you can get different runtime
> behavior with datums created with a beta version. Seems more clear to just
> require a pg_dump + restore.
I vote for going with your patch, and breaking compatibility for the
reasons stated here (though I'm skeptical of the claims about cache
benefits, FWIW).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-24 01:06:29 | Re: jsonb format is pessimal for toast compression |
| Previous Message | Andrew Dunstan | 2014-09-24 00:20:15 | Re: JsonbValue to Jsonb conversion |