Message-ID: <gh-pgjdbc-pgjdbc-3889-c3622321091@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sun, 07 Dec 2025 15:23:26 +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: 3622321091
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-12-07T15:23:39Z
X-GitHub-Issue: 3889
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3889#issuecomment-3622321091
Content-Type: text/plain; charset=utf-8

> There can be a resource leak if lot of prepared statements unused been prepared on a long lived backend

The statement cache has limited size per connection, so it is not a memory leak.

> On schema change it can cause an Error - "Cached plan must not change result type".

That is out of control for the jdbc driver. Please ask PostgreSQL database developers to fix the issue.