| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Nicolas Paris <niparisco(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: array size exceeds the maximum allowed (1073741823) when building a json |
| Date: | 2016-06-08 05:56:03 |
| Message-ID: | CAB7nPqRdN=7xU14Q=2=fho_apR0TEoKtWyHZip0HSMkYsOUp-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jun 7, 2016 at 10:03 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> 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.
And there are other things to consider on top of that, like the
maximum allocation size for palloc, the maximum query string size,
COPY, etc. This is no small project, and the potential side-effects
should not be underestimated.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-08 06:04:19 | Re: array size exceeds the maximum allowed (1073741823) when building a json |
| Previous Message | David G. Johnston | 2016-06-08 05:33:24 | Re: Performance of LIKE/NOT LIKE when used in single query |