Re: jsonb format is pessimal for toast compression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(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-29 16:30:40
Message-ID: 5861.1412008240@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Sep 25, 2014 at 02:39:37PM -0400, Tom Lane wrote:
>> BTW, it seems like there is consensus that we ought to reorder the items
>> in a jsonb object to have keys first and then values, independently of the
>> other issues under discussion. This means we *will* be breaking on-disk
>> compatibility with 9.4beta2, which means pg_upgrade will need to be taught
>> to refuse an upgrade if the database contains any jsonb columns. Bruce,
>> do you have time to crank out a patch for that?

> Yes, I can do that easily. Tell me when you want it --- I just need a
> catalog version number to trigger on.

Done --- 201409291 is the cutover point.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-09-29 17:18:31 Re: jsonb format is pessimal for toast compression
Previous Message David E. Wheeler 2014-09-29 16:17:15 Re: json (b) and null fields