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 CAM3SWZSYT6c13Zdrj4tDyoBR51M5ca9CJ8bf74T36=95j7GcKQ@mail.gmail.com
Whole thread Raw
In response to Re: jsonb format is pessimal for toast compression  (Ants Aasma <ants@cybertec.at>)
List pgsql-hackers
On Fri, Aug 8, 2014 at 12:41 PM, Ants Aasma <ants@cybertec.at> wrote:
> I don't think binary search is the main problem here. Objects are
> usually reasonably sized, while arrays are more likely to be huge. To
> make matters worse, jsonb -> int goes from O(1) to O(n).

I don't think it's true that arrays are more likely to be huge. That
regression would be bad, but jsonb -> int is not the most compelling
operator by far. The indexable operators (in particular, @>) don't
support subscripting arrays like that, and with good reason.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: jsonb format is pessimal for toast compression
Next
From: Peter Geoghegan
Date:
Subject: Re: jsonb format is pessimal for toast compression