Message-ID: <gh-pgjdbc-pgjdbc-3724-c3051708389@github.com>
From: "papegaaij (@papegaaij)" <noreply+papegaaij@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 09 Jul 2025 08:38:51 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3724: Regression: FATAL:  simple query "BEGIN" arrived before ending an extended query message
In-Reply-To: <gh-pgjdbc-pgjdbc-3724@github.com>
References: <gh-pgjdbc-pgjdbc-3724@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: papegaaij
X-GitHub-Comment-Id: 3051708389
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3724
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3724#issuecomment-3051708389
Content-Type: text/plain; charset=utf-8

@vlsi If I'm not mistaken, pgjdbc autosave needs to be enabled explicitly. We do not use autosave, so even though it might be related to the other ticket, the cause must be somewhere else. Also, we are very confident this change was introduced between 42.7.5 and 42.7.7 as we consistently trigger the error on the latter version and do not on the first.