Re: jsonb format is pessimal for toast compression
От | Peter Geoghegan |
---|---|
Тема | Re: jsonb format is pessimal for toast compression |
Дата | |
Msg-id | CAM3SWZTszbGY-Td=AdXM5E3Wp2iuuqj1T3_6mWEVhQHZEXcz1g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: jsonb format is pessimal for toast compression (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: jsonb format is pessimal for toast compression
|
Список | pgsql-hackers |
On Fri, Sep 19, 2014 at 5:40 AM, Heikki Linnakangas <hlinnakangas@vmware.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
В списке pgsql-hackers по дате отправления: