Message-ID: <gh-pgjdbc-pgjdbc-3462-c2557635667@github.com>
From: "butopcu (@butopcu)" <noreply+butopcu@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 20 Dec 2024 19:54:33 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3462: Next Method of PgResultSet Throws NullPointerException Instead of SQLException
In-Reply-To: <gh-pgjdbc-pgjdbc-3462@github.com>
References: <gh-pgjdbc-pgjdbc-3462@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: butopcu
X-GitHub-Comment-Id: 2557635667
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3462
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3462#issuecomment-2557635667
Content-Type: text/plain; charset=utf-8

@davecramer

Yes, our connection pool mechanism is not closing and reopening connections.  
When a Thread takes a connection, it is removed from the free connection list.  
After the Thread completes its task, we close the `ResultSet` and `Statement`, then push the connection back to the free connection list. After that, any other thread can take and reuse the same connection.