Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAGFY-00033V-L2 for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:36: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 1bAGFY-0007yb-7Q for pgsql-performance@arkaria.postgresql.org; Tue, 07 Jun 2016 12:36:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bAGFX-0007wo-FO for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:36:51 +0000 Received: from mail-wm0-x233.google.com ([2a00:1450:400c:c09::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAGFU-00037k-Pj for pgsql-performance@postgresql.org; Tue, 07 Jun 2016 12:36:50 +0000 Received: by mail-wm0-x233.google.com with SMTP id v199so17444090wmv.0 for ; Tue, 07 Jun 2016 05:36:48 -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=cqrICw7LEMrQ7vUYGPKj6brUqRDrCJ5YjP4JyURLOlE=; b=J+8yCfrcwrqVnzCGBXPD4FwXoLOw0nsFcX7jizR7o/SRXcglVzeFdUbIO3nv32XxQp 1P4vE5IpYShFM/2vjwgtBm1+Y5o10g4ru70ilz2m/AVyQW0WukKnAyXCSqg3/3Tcy/lI CVeZbFEPKFJiRC0L3JiZGXFc0uei2ucRVPHSXWNq1a/xsH20mrcbe4ZUVJU7DWU4HXoz 5z8qsxYPZtbMH7KTNYD+89MmVgTn5ee9hX5hcKLGK68r2IeNNXSTzytpAqRNp90KlWHf AfNxdP/65+DsYTI0UxDBAB8FIXNATKXxb898fgdjRM8HYeg8W431hPoazXiXglZBo+iI rcFQ== 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=cqrICw7LEMrQ7vUYGPKj6brUqRDrCJ5YjP4JyURLOlE=; b=a+9KdUAc/Peo31MIvBv9+bsdROjnKudmnSb6JE/5H0f8FgBHEi+dzd2ri2NmQ0iFD1 ioitAvNsBS3pfi5JqrUvgidHqdf5nF3aZvfhU/YvvEAUTW+Tqn3LgButP8I57S0gq9Qe Sc97ZUYhP2mk1mf/YLSKjuY4BBQwU3LrJbjS5/URZSDeMQCuRW1nbtqpqOt+FOK5I+3Z ZhZ4nQw9+xliZWeVIq8IQXy9pK2Fsv9IswUE6JnS9e3Eb63D/k23XKrZD6Lu7QRVH6Iq PmFIhQ9ymyTxuZ7G0Kh40HHZfSQ6s2m37zWClMrwSYx5mRVjAxI3Ips7Y0cm24Nu7o3k M4bA== X-Gm-Message-State: ALyK8tL/aX5j8nyHNbqq1pE3RQ7zEzMk3TPJDuRvZxllsKXtRHXUqsNixpP57PeK3holslkUQgLw7QDodr3MDA== X-Received: by 10.28.178.70 with SMTP id b67mr2528721wmf.13.1465303007210; Tue, 07 Jun 2016 05:36:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.133.196 with HTTP; Tue, 7 Jun 2016 05:36:46 -0700 (PDT) In-Reply-To: References: From: Nicolas Paris Date: Tue, 7 Jun 2016 14:36:46 +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=001a114420243bb33c0534af71b1 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 --001a114420243bb33c0534af71b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 per= iod. >> 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 ? Then I must build it with an external tool ? =E2=80=8B > > =E2=80=8BIt doesn't matter that the data never actually is placed into a = physical > table. > > David J. > > --001a114420243bb33c0534af71b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2016-06-07 14:31 GMT+02:00 Davi= d G. Johnston <david.g.johnston@gmail.com>:
On Tue, Jun 7, 2016 at 7:44 AM, Nicola= s Paris <= ;niparisco@gmail.c= om> 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 t= he period (huge dataset) I get this error:
SQL E=
RROR[54000]
ERROR: array size exceeds the maxi= mum allowed (1073741823)


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

It means a json cannot exceed 1GB in postgresql, right ?<= br>
Then I must build it with an external = tool ?
=E2=80=8B
=C2=A0

=
=E2=80=8BIt doesn't matter that the data never actually is = placed into a physical table.

David J.

=

--001a114420243bb33c0534af71b1--