Message-ID: <gh-pgjdbc-pgjdbc-3993-c4109687444@github.com>
From: "qinarmy-zoro (@qinarmy-zoro)" <noreply+qinarmy-zoro@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 23 Mar 2026 10:48:39 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
In-Reply-To: <gh-pgjdbc-pgjdbc-3993@github.com>
References: <gh-pgjdbc-pgjdbc-3993@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: qinarmy-zoro
X-GitHub-Comment-Id: 4109687444
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3993
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3993#issuecomment-4109687444
Content-Type: text/plain; charset=utf-8

> I suppose not, but if you aren't going to use the API, why would you expect the rest of the API to work ?

Why can't I use the START TRANSACTION command while using a cursor? Does PostgreSQL prohibit me from using it?

Is it unreasonable to add a single line of code just to check if the current connection is inside a database transaction block？