On Sat, Jun 03, 2023 at 08:36:02PM -0400, Heikki Linnakangas wrote:
> 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.
Latency-sensitive issue perhaps? I am unsure of what we could do here
without more evidence and/or ways to reproduce the problem. Likely as
a small-ish libpq program and something to fake a delay?
--
Michael
