Message-ID: <gh-pgjdbc-pgjdbc-2525-c1143506616@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 01 Jun 2022 11:51:29 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #2525: fix: support queries with up to 65535 (inclusive) parameters
In-Reply-To: <gh-pgjdbc-pgjdbc-2525@github.com>
References: <gh-pgjdbc-pgjdbc-2525@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 1143506616
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2525
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/2525#issuecomment-1143506616
Content-Type: text/plain; charset=utf-8

Ok, the reason is "org.postgresql.test.jdbc2.RefCursorFetchTest |   | PASSED | 2h 57m 24.946s"

In other words, it does not look like a code regression, rather it looks like RefCursorFetchTest is extremely slow for unknown reasons.