Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAGaq-0004fh-0z for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:58:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAGap-0001uT-Fw for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:58:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bAGao-0001tw-Gr for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:58:50 +0000 Received: from mail-oi0-x22c.google.com ([2607:f8b0:4003:c06::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAGaj-0004J2-HE for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:58:49 +0000 Received: by mail-oi0-x22c.google.com with SMTP id s139so35768522oie.2 for ; Tue, 07 Jun 2016 05:58:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qI+JHVNNq1U6RDoJyDHhcvmwmw73MDSfhrxojctM6tU=; b=M6OYpsYtJVc/ztSO6+AUHvhA3H4mBrQ6jMmtdK+W9BiPUmn7nMpP5I8zgnUnssYFeb thT9v0yQRj1ZNs3pwESgyNFBr6CgQTvAvL+QqtGZvQd57TOgJTET2o4Aytkt2qPiO2pH K4JMsZrzCMroDZOqMt6/grNT+Jrg3LjIIKJ0o+szps2Xj75UdC4bVftC0r4vAWNFQeCJ fAnyMvKJ99SR26FWm/N/18Jnwxb/3EhPoJJa+W7NQURA2hBttYgf7sXjGnltHPAPvazR OHqfzqlCnbXyrvp5K0ibRt2BiucsZCII8/E2qO+7JDuiGHxlqUKAU9jGuJmNHpRWe3Sl xUow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qI+JHVNNq1U6RDoJyDHhcvmwmw73MDSfhrxojctM6tU=; b=AQAQj01tZTVTVMOt46lGHZJaOkzdgzTnYcVl5etJSn9Xsxde0HL1Bta26f+U3Kces+ lS2ZTC3idECYqP8rqnlSsqllGR8qo6C+Msrdy7omNvyeHf3ZXv3sLj8xvgVOf+9YAlpp 3KLNLONQhrfn6D/hH9QAeFMTiHFKlWCUuNaxPSmvVFUsQldNnRP78Rfo7o2/i/XO7oHw kivioGzKoPjdYdw6YktXgoPTruWCWqPMah27R/8QjmSVJYYkrCI/JSJSi9ZKdrnd17ej /FAUzRhf6DKvj/jBiEE0qPIRVS/OKE9YbhIlFKaYVOfCw+v0hCJ95+aKwh1JpGE8yErB gfRw== X-Gm-Message-State: ALyK8tJOtAGWlWHDkUMs2QT+gsxWzIFWXDPGQSNnWnFP84jN/B2ZrDMZB6posGw3+JJtnxnRbujW6vF3OMR2+w== X-Received: by 10.157.16.93 with SMTP id o29mr5570400oto.155.1465304323757; Tue, 07 Jun 2016 05:58:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.34.104 with HTTP; Tue, 7 Jun 2016 05:58:43 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Tue, 7 Jun 2016 08:58:43 -0400 Message-ID: Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json To: Nicolas Paris Cc: pgsql-performance Content-Type: multipart/alternative; boundary=001a113d0f08b49afc0534afbf34 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --001a113d0f08b49afc0534afbf34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jun 7, 2016 at 8:42 AM, Nicolas Paris wrote: > > > 2016-06-07 14:39 GMT+02:00 David G. Johnston = : > >> On Tue, Jun 7, 2016 at 8:36 AM, Nicolas Paris >> wrote: >> >>> 2016-06-07 14:31 GMT+02:00 David G. Johnston >> >: >>> >>>> On Tue, Jun 7, 2016 at 7:44 AM, Nicolas Paris >>>> wrote: >>>> >>>>> Hello, >>>>> >>>>> I run a query transforming huge tables to a json document based on a = period. >>>>> It works great for a modest period (little dataset). >>>>> However, when increasing the period (huge dataset) I get this error: >>>>> >>>>> SQL ERROR[54000] >>>>> ERROR: array size exceeds the maximum allowed (1073741823) >>>>> >>>>> =E2=80=8Bhttps://www.postgresql.org/about/=E2=80=8B >>>> >>>> =E2=80=8BMaximum Field Size: 1 GB=E2=80=8B >>>> >>> >>> It means a json cannot exceed 1GB in postgresql, right ? >>> >> >> =E2=80=8BYes=E2=80=8B >> >> >>> Then I must build it with an external tool ? >>> =E2=80=8B >>> >>> >> >> =E2=80=8B=E2=80=8BYou have to do something different. Using multiple co= lumns and/or >> multiple rows might we workable. >> > > =E2=80=8BCertainly. Kind of disappointing, because I won't find any json = builder > as performant as postgresql.=E2=80=8B > > =E2=80=8B > > Will this 1GO restriction is supposed to increase in a near future ?=E2= =80=8B > > There has been zero chatter on the public lists about increasing any of the limits on that page I linked to. David J. =E2=80=8B --001a113d0f08b49afc0534afbf34 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Ju= n 7, 2016 at 8:42 AM, Nicolas Paris <niparisco@gmail.com> wrote:


2016-06-07 14:= 39 GMT+02:00 David G. Johnston <david.g.johnston@gmail.com>= ;:
On Tue, Jun 7, 2016 at 8:36 AM, Nicolas Paris <niparisco@gmail.com> wrote:
2016-06-07 = 14:31 GMT+02:00 David G. Johnston <david.g.johnston@gmail.com= >:
On Tue, Jun 7,= 2016 at 7:44 AM, Nicolas Paris <niparisco@gmail.com> wrote:
Hello,

=
I run a query transforming huge tables to a json document based on a period=
.
It works great for a modest period (little dataset). 
However, when=
 increasing the period (huge dataset) I get this error:
SQL ERROR[54000]
ERROR: array size exc= eeds the maximum allowed (1073741823)


=
=E2=80=8BMaximum= Field Size: 1 GB=E2=80=8B

It means a json cannot exceed 1GB in postgresql, right ?
<= /div>

<= div>
=E2=80=8BYes=E2= =80=8B
=C2=A0
Then I must build it with an external tool ?
=E2=80=8B
= =C2=A0

=E2=80=8B= =E2=80=8BYou have to do something different.=C2=A0 Using multiple columns a= nd/or multiple rows might we workable.

=E2=80=8BCertainly. Kind of disappointing, becaus= e I won't find any json builder as performant as postgresql.=E2=80=8B=C2=A0
=E2=80=8B

Will this 1GO restriction is supposed to inc= rease in a near future ?=E2=80=8B


There has been zero chatter = on the public lists about increasing any of the limits on that page I linke= d to.

David J.
=E2=80=8B
=C2=A0
<= /div> --001a113d0f08b49afc0534afbf34--