public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: Nicolas Paris <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: pgsql-performance <[email protected]>
Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json
Date: Wed, 08 Jun 2016 02:04:19 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAB7nPqRdN=7xU14Q=2=fho_apR0TEoKtWyHZip0HSMkYsOUp-Q@mail.gmail.com>
References: <CA+ssMORBYVFxedSXVVxL5VPeo=9AbYRQ-zbpuKJm6vEjmJ1CFA@mail.gmail.com>
<CAKFQuwbjwyaaFUOEzxoYCBDm25ujOayCniwiWimPML_A_VaGYA@mail.gmail.com>
<CA+ssMOT04Wg+OGfSc5AUk8nVQOxkVS6=CD-h7bH-pAH-ix50cw@mail.gmail.com>
<CAKFQuwZEkX6o2mv2Ekqp8DpAs9F0bMsBnvQxzJGUr+SS6t2yTg@mail.gmail.com>
<CA+ssMOSdHUTMWqswZ4njAgtf4vpAkuZ8duH7znB0G5pEswa38w@mail.gmail.com>
<WM!d318efe352c6e124baed8053dba915699725885de80c4fdd70cff903faba6afc6e6233ba053fb428df2d56162a988029!@mailstronghold-1.zmailcloud.com>
<[email protected]>
<CAB7nPqRdN=7xU14Q=2=fho_apR0TEoKtWyHZip0HSMkYsOUp-Q@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-performance>
Michael Paquier <[email protected]> writes:
> On Tue, Jun 7, 2016 at 10:03 PM, Josh Berkus <[email protected]> wrote:
>> On 06/07/2016 08:42 AM, Nicolas Paris wrote:
>>> 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.
It's also fair to doubt that client-side code would "just work" with
no functionality or performance problems for such large values.
I await with interest the OP's results on other JSON processors that
have no issues with GB-sized JSON strings.
regards, tom lane
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox