Re: array size exceeds the maximum allowed (1073741823) when building a json

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Nicolas Paris <niparisco(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json
Date: 2016-06-07 13:03:20
Message-ID: 5756C618.1070802@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 06/07/2016 08:42 AM, Nicolas Paris wrote:
> ​​You have to do something different. Using multiple columns and/or
> multiple rows might we workable.
>
>
> ​Certainly. Kind of disappointing, because I won't find any json builder
> as performant as postgresql.​

That's nice to hear.

> Will this 1GO restriction is supposed to increase in a near future ?​

Not planned, no. Thing is, that's the limit for a field in general, not
just JSON; changing it would be a fairly large patch. It's desireable,
but AFAIK nobody is working on it.

--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2016-06-07 13:24:10 Re: Locking concurrency: select for update vs update
Previous Message David G. Johnston 2016-06-07 12:58:43 Re: array size exceeds the maximum allowed (1073741823) when building a json