Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAGMq-0003Yx-FR for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:44:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAGMq-0005xI-1r for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:44:24 +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 1bAGL3-0003zb-Lu for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:42:33 +0000 Received: from mail-wm0-x22e.google.com ([2a00:1450:400c:c09::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAGKz-0003w4-Vs for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:42:33 +0000 Received: by mail-wm0-x22e.google.com with SMTP id r5so8770029wmr.0 for ; Tue, 07 Jun 2016 05:42:29 -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=EhaEFSPARwnYwK1hNqM7kYFUvPHxjYfrSlyjtwopUQU=; b=0ABP3oq2pXfvhXYm5feWZOUTN/4Ujn1/ZnCRYuFGe5gjpFXPQ8OnTkciLUljrUs70O aX15pFl4YcheZ+dSgu2UftByjrFS71NKuH3lw//ptIRtKGVqkX+xYMttki6un1c2mA98 f2o+UijltffaGoEX19Pwct79SHRlFy19RkgC8w8CWvx2xSGilizrWIfAPanIWfdt7HLb YTfKN3jLlLqxjnUTq8BwpaYYx/BL/lNwxhjuUQKhJhiG7PEZdqC4he2HHrGaeqjt0yky m/UOhI5XovUUk0XTHYeieFbGmega4t8vEniR5XryG88/wjoQyQT10vdLDYuoGOktg6dn YHbg== 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=EhaEFSPARwnYwK1hNqM7kYFUvPHxjYfrSlyjtwopUQU=; b=Mt2v/PQYwGDvBAZxNAevyR7AJtvYB4GupKpdi3hL0H17GtyT6YOFnwz8H4ovv5sOk7 vluklmnbo45/hFlPQYE1jLbMD1trrrOHIR9Hc3OY3qzbFT/sErBN09avtKKWsNrbkVjE SkaQamIKPnmXjq5+sK83sNII5RjWZFqDKhBFJXtqvDMGcFuMDsU2iIALkt3qjVeB+Wpi +tRwzu6JJZcxRflbWgiCqi/f3DP63jnIaQaywdBKRohpxHbxN42RYEe1wdMzivpvCDLK oStm5toPqYbmXE5tNXcF/W6WFynjBD9xJs5Th8uS2FrvrSqs6ITbSVu6D+pryA9jGqIP lM/A== X-Gm-Message-State: ALyK8tKz+ciyHFbI2yltX1iFu89r/ajxW96+MIEVVHefnr1jRp+KTvHwIQ0XCQA8PzxoKeqUVnusivVaXHfV0Q== X-Received: by 10.28.144.7 with SMTP id s7mr2574216wmd.103.1465303348963; Tue, 07 Jun 2016 05:42:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.133.196 with HTTP; Tue, 7 Jun 2016 05:42:28 -0700 (PDT) In-Reply-To: References: From: Nicolas Paris Date: Tue, 7 Jun 2016 14:42:28 +0200 Message-ID: Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json To: "David G. Johnston" Cc: pgsql-performance Content-Type: multipart/alternative; boundary=001a1145aa849a701d0534af852b 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 --001a1145aa849a701d0534af852b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 p= eriod. >>>> 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 col= umns and/or > multiple rows might we workable. > =E2=80=8BCertainly. Kind of disappointing, because I won't find any json bu= ilder 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 > David J. > > --001a1145aa849a701d0534af852b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2016-06-07 14:39 GMT+02:00 David G. Johnston <d= avid.g.johnston@gmail.com>:
On Tue, Jun 7, 2= 016 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, Nico= las Paris &= lt;niparisco@gmail= .com> wrote:
<= span>
Hello,

I run a query transfor=
ming huge tables to a json document based on a period.
It works great fo=
r 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 allow=
ed (1073741823)


=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
=C2=A0
=
Then I must = build it with an external tool ?
=E2=80=8B
=C2=A0

=E2=80=8B=E2=80=8BYou hav= e to do something different.=C2=A0 Using multiple columns and/or multiple r= ows might we workable.

<= div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;color:rg= b(0,51,51);display:inline">=E2=80=8BCertainly. Kind of disappointing, becau= se I won't find any json builder as performant as postgresql.=E2=80=8B<= /div>=C2=A0
=E2=80=8B

Will this 1GO restr= iction is supposed to increase in a near future ?=E2=80=8B


David J.


--001a1145aa849a701d0534af852b--