Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAWV2-0008PX-Tt for pgsql-performance@arkaria.postgresql.org; Wed, 08 Jun 2016 05:57:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAWV2-00014E-Gr for pgsql-performance@arkaria.postgresql.org; Wed, 08 Jun 2016 05:57:56 +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 1bAWTN-0007cJ-OU for pgsql-performance@postgresql.org; Wed, 08 Jun 2016 05:56:13 +0000 Received: from mail-vk0-x235.google.com ([2607:f8b0:400c:c05::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAWTG-0001df-Q2 for pgsql-performance@postgresql.org; Wed, 08 Jun 2016 05:56:13 +0000 Received: by mail-vk0-x235.google.com with SMTP id d64so149512131vkb.0 for ; Tue, 07 Jun 2016 22:56:06 -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=wrIYcrWpPMBCyJnSRLdnySKwm2etCbceSkG8SzXS9jc=; b=El6nzuNApu9a7yqVw4Md52Q3Ax2CoWRn5qxMN96tyG+fe5vP+is6bB81vNhjlBn2fX Z0jejC7qYlL8XznqMSAV1QEkAOtnxPD1T0a9tH8MDLRlRWvi66NtjCTk1tcwu3HNyPNg ti10GiD6+iMzWRf414IkHD9dWMFJvaj2CGpTI32xFY8t91vGP6ikh5BNo6tdBkHWWtaU 6egPSaLomrZ26aqoKjFkv/ZwxAbfWzHVTcMAo8ex5GPuSXrLXVElzBpuh0gQI8kY0VAm xTzaFOCK+bTtIfBL0D527mjZwL8jD/1BVPrRG62IgQE4xxlGcpmEinhs2UY6b0G7UhV5 dF+g== 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=wrIYcrWpPMBCyJnSRLdnySKwm2etCbceSkG8SzXS9jc=; b=FvWtL45aSiEaW2imo8xyQpOAcQxlUkMmoFAzUvHPPN5oIjpRi9b3AkSDj7KBgSPmTH tdBo5qxWMcPFHyB0mZMmm+b2CnHsf3vdIYvbh9SCHqiUY8lMKcJhQ5B12npGfmgFd3XB k+dV3fBCEngQQGEyhFm2XqHO6S/MUEfpTBKSxEEygbo/YOL7yPl5B20LcQrD99JEFG4f wyad7hXap27ObsXChxwu3sAr5N606eubPgvC+7TA/zEbvVuFRHJ3NQ7NcBmg9AY6IJBH kS136VzPkt7b0mDTY1YZU94TgiW/hE5pAUwbNdV1nOvBc6wogxHBhZpOImmJAbIMf3zT DtYg== X-Gm-Message-State: ALyK8tKS4U0u1I8JN2EFV3ggqr+7ZWN21Go7PAtHLfCFgekGydzHDpRX+y2aBKcwqguXg3lstvnaekd6loZaVw== X-Received: by 10.159.33.175 with SMTP id 44mr1519705uac.142.1465365364501; Tue, 07 Jun 2016 22:56:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.137.197 with HTTP; Tue, 7 Jun 2016 22:56:03 -0700 (PDT) In-Reply-To: <5756C618.1070802@agliodbs.com> References: <5756C618.1070802@agliodbs.com> From: Michael Paquier Date: Wed, 8 Jun 2016 14:56:03 +0900 Message-ID: Subject: Re: array size exceeds the maximum allowed (1073741823) when building a json To: Josh Berkus Cc: Nicolas Paris , "David G. Johnston" , pgsql-performance Content-Type: text/plain; charset=UTF-8 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 On Tue, Jun 7, 2016 at 10:03 PM, Josh Berkus 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance