Re: BUG #17953: Libpq can stall indefinitely with non-tls localhost (127.0.0.1) connection

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: olli(dot)pekkola(at)grundium(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17953: Libpq can stall indefinitely with non-tls localhost (127.0.0.1) connection
Date: 2023-06-04 00:36:02
Message-ID: 193e3d03-cbd0-145b-4ab3-9519391e591f@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 01/06/2023 07:27, PG Bug reporting form wrote:
> I can craft a POC if neccessary, precise steps are not super clear at this
> time. But the PQexecFinish() stalled several times withtout TLS with the
> following stack (with TLS, not a single instance of this is observed):

Yeah, I think we'll need a self-contained repro to debug this. Or at
least a lot more details on what the query is, what the server is doing
when that happens, etc. A wireshark trace might be useful.

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-06-04 12:20:56 BUG #17960: pg_dump does not backup generated columns correctly.
Previous Message PG Bug reporting form 2023-06-03 19:00:01 BUG #17959: amcheck fails to find a matching index tuple for an invisible heap tuple