| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | BATBAATAR Dorjpalam <htgn(dot)dbat(dot)95(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq |
| Date: | 2025-06-10 00:40:38 |
| Message-ID: | 652538.1749516038@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Indeed, it looks like we'd better disable the round-down for GSSAPI
> too, because pg_GSS_write has exactly this same API requirement that
> caller has to pass at least as much data as last time.
So in short, I propose the attached patch. I chose to disable the
round-down behavior for all TCP connections, including ones that
use neither SSL nor GSSAPI. I'm not sure if it's worth worrying
too much about that case.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v1-fix-bug-18907.patch | text/x-diff | 3.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2025-06-10 02:09:22 | RE: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 |
| Previous Message | Lowell Hought | 2025-06-09 23:35:13 | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 |