Message-ID: <gh-pgjdbc-pgjdbc-3840-c3415311373@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 17 Oct 2025 12:14:26 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3840: Periodic latency spikes to Postgres in large scale deployment
In-Reply-To: <gh-pgjdbc-pgjdbc-3840@github.com>
References: <gh-pgjdbc-pgjdbc-3840@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 3415311373
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3840
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3840#issuecomment-3415311373
Content-Type: text/plain; charset=utf-8

From what I can see, the shared time is being used to close an otherwise not closed connection. It could be waiting to send the close message? 

@vlsi may have other ideas