Message-ID: <gh-pgjdbc-pgjdbc-3889-c3622250874@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sun, 07 Dec 2025 14:37:16 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3889: JDBC Not Sending CLOSE packet
In-Reply-To: <gh-pgjdbc-pgjdbc-3889@github.com>
References: <gh-pgjdbc-pgjdbc-3889@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3622250874
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3889
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3889#issuecomment-3622250874
Content-Type: text/plain; charset=utf-8

pgjdbc has a cache of statements, so it is able to reuse sever-side statements even in the case of `stmt.close`.

See https://stackoverflow.com/questions/32297503/whats-the-life-span-of-a-postgresql-server-side-prepared-statement/32300222#32300222

Why do you expect `CLOSE` message?