Re: jsonb format is pessimal for toast compression - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: jsonb format is pessimal for toast compression
Date
Msg-id CAM3SWZTszbGY-Td=AdXM5E3Wp2iuuqj1T3_6mWEVhQHZEXcz1g@mail.gmail.com
Whole thread Raw
In response to Re: jsonb format is pessimal for toast compression  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: jsonb format is pessimal for toast compression
List 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 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: JsonbValue to Jsonb conversion
Next
From: Tom Lane
Date:
Subject: Re: jsonb format is pessimal for toast compression