Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: htgn(dot)dbat(dot)95(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
Date: 2025-04-29 18:48:01
Message-ID: CAOYmi+kPBjLcHqbY1PK2bnvVJ90dBbJAp0vBfrDNHTdmscxvbg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Apr 29, 2025 at 11:06 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Agreed -- but also, let us know if the answer is "no, I can't", or if
you get stuck and need some additional collaboration. These corner
cases can be really nasty to track down and record.

Thanks,
--Jacob

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Japin Li 2025-04-30 06:38:14 Re: pg_restore error with partitioned table having exclude constraint
Previous Message Francisco Olarte 2025-04-29 18:44:21 Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan