Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <psycopg-owner+archive@lists.postgresql.org>)
	id 1gHk6s-0000i9-VC
	for psycopg@arkaria.postgresql.org; Wed, 31 Oct 2018 06:36:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <psycopg-owner+archive@lists.postgresql.org>)
	id 1gHk6r-00024D-18
	for psycopg@arkaria.postgresql.org; Wed, 31 Oct 2018 06:36:09 +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.89)
	(envelope-from <tshelver@gmail.com>)
	id 1gHk6q-000246-SV
	for psycopg@lists.postgresql.org; Wed, 31 Oct 2018 06:36:08 +0000
Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tshelver@gmail.com>)
	id 1gHk6o-0007g5-VH
	for psycopg@postgresql.org; Wed, 31 Oct 2018 06:36:08 +0000
Received: by mail-ed1-x534.google.com with SMTP id e5-v6so12621232eds.6
        for <psycopg@postgresql.org>; Tue, 30 Oct 2018 23:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:from:date:message-id:subject:to;
        bh=5CgSOkhPy71yLIchWNfqQfhRSHL46rN/dGwXuqQMcSg=;
        b=U1vTWwm+h4RIqAeS4wVtCmQ6XJG9wOlEaYSTlDgfSmLeOvddRg6GL7QJxZdXOttz1z
         XLCVlAp2ExMtU3/iO8kf9+uDjwnmcORntZjslm6oAhIHaHdqmgkLaT5rEWF2PPqKRaB6
         YOVmxlJPGnG1tM32Rn7fsro2vwKD1P7gggLJwYJtm7LibWFHaL0/uj/8cMnZesi1n47W
         CjUJzkFCJErZThZqtIa1vsI59/2HNaLFhkvlsF3DJZo+iL3y3bWkgLUm8YCW5Au57BR3
         i0oxoDQVkYJme/okZtAICVaKfLYwDduo52mNyfysOPzrlDCt5wyNnfNm0Fhg2qCjsr55
         iP+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=5CgSOkhPy71yLIchWNfqQfhRSHL46rN/dGwXuqQMcSg=;
        b=QJruLWgkqGmAK7UpvMoU08mWcvhD9+//D4y6VIwLI9kIvX9kdmdXikpGMmdQXGywGL
         OaRg3xiRBiv1h2bEeg9yA2KSL1pyWgmmwCaPNIYbFC0SgP3fdA3nfBuAy8jur63Oj4XH
         40EiA/DbPKRtTGC1xub1aGOKDepS/RAk4bzTxRJhjzc6oCuhvFXOT5MygdMlugQ7GQls
         2wBgs2rP78S5DZ5v9w82Ic/vOEAoulVlcKmQaaUkcvhnuE/J8DeMZvAVAMe1zYHJ8mMJ
         DjKZ117mo8/Io/ze/dKIzLTlDeza5lv18IVLCsAU21M9kcWJma8ZqeemnNZOI7gjcQHM
         oi+g==
X-Gm-Message-State: AGRZ1gK/xSQ5Sh3aEcQZOK/KMNN7BhWRrdLBpdemg4bWdwsfzNV0pUR4
	TsxKb6PYye1ywXeOgG3ilbBF8PEwSpRRf0K1oOpYGSG2
X-Google-Smtp-Source: 
 AJdET5dqnVc+fRk8Ec4Bc7HeDyCY83RUr7DmREMvz77BtYvFsIx42rIC/I0Ea3XOzVDFU0w1kuv0viV8MmBHnQIzx7U=
X-Received: by 2002:a17:906:4ac4:: with SMTP id
 u4-v6mr725823ejt.202.1540967764660;
 Tue, 30 Oct 2018 23:36:04 -0700 (PDT)
MIME-Version: 1.0
From: Tony Shelver <tshelver@gmail.com>
Date: Wed, 31 Oct 2018 08:35:55 +0200
Message-ID: 
 <CAG0dhZAZkq9LM_8GVrzk63FGKgsJ_+cb7nFA=OzJX8C6oQRQCA@mail.gmail.com>
Subject: Max message size / constraints?
To: psycopg@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000003919710579808404"
List-Id: <psycopg.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:psycopg@lists.postgresql.org>
List-Owner: <mailto:psycopg-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/psycopg>
Precedence: bulk

--0000000000003919710579808404
Content-Type: text/plain; charset="UTF-8"

I am calling postgresql functions / stored procedures to insert / update
data, passing the data in jsonb format.

To avoid roundtripping for each record to be inserted / updated, I would
like to compose multiple records in a single jsonb parameter.

Is there a limit in psycopg2 as to the size of the parameter?


Thanks

Tony

--0000000000003919710579808404
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am calling postgresql functions / stored procedures to i=
nsert / update data, passing the data in jsonb format.<div><br></div><div>T=
o avoid roundtripping for each record to be inserted / updated, I would lik=
e to compose multiple records in a single jsonb parameter.</div><div><br></=
div><div>Is there a limit in psycopg2 as to the size of the parameter?</div=
><div><br></div><div><br></div><div>Thanks</div><div><br></div><div>Tony</d=
iv></div>

--0000000000003919710579808404--