Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u9pLK-006leR-AH for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Apr 2025 18:06:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u9pLI-009DfA-48 for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Apr 2025 18:06:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u9pLH-009Df2-Rz for pgsql-bugs@lists.postgresql.org; Tue, 29 Apr 2025 18:06:04 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u9pLH-000DsE-04 for pgsql-bugs@lists.postgresql.org; Tue, 29 Apr 2025 18:06:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 53TI606P1055822; Tue, 29 Apr 2025 14:06:00 -0400 From: Tom Lane To: htgn.dbat.95@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq In-reply-to: <18907-d41b9bcf6f29edda@postgresql.org> References: <18907-d41b9bcf6f29edda@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 29 Apr 2025 16:35:36 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1055820.1745949960.1@sss.pgh.pa.us> Date: Tue, 29 Apr 2025 14:06:00 -0400 Message-ID: <1055821.1745949960@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > When using libpq to transfer large amounts of data to the server in pipeline > mode (registering with COPY), an error "SSL error: bad length" > sometimes occurs. Could you provide a self-contained test case demonstrating such failures? This is not the kind of code that we like to change on the basis of undocumented claims. regards, tom lane