Message-ID: <gh-pgjdbc-pgjdbc-2525-c1143593457@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 01 Jun 2022 13:10:52 +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: 1143593457
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-1143593457
Content-Type: text/plain; charset=utf-8

It all means "fix close refcursors" was OK, and there's something else going slow with CI env.

The worst thing is that if I launch just `org.postgresql.test.jdbc2.RefCursorFetchTest` in Actions, then it takes ~16 or so seconds.

So it looks like some of the tests before RefCursorFetchTest triggers a bad condition, so subsequent tests become slow.