Message-ID: <gh-pgjdbc-pgjdbc-3724-c3051773696@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 09 Jul 2025 08:58:09 +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: vlsi
X-GitHub-Comment-Id: 3051773696
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-07-09T08:58:22Z
X-GitHub-Issue: 3724
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3724#issuecomment-3051773696
Content-Type: text/plain; charset=utf-8

I'm sure the commit that altered the behaviour was https://github.com/pgjdbc/pgjdbc/pull/3655/files#diff-cfe87ac6bfaa171dc41659f7bd2368cf9fc6d6d6531fade06f315ed58064986fL321-L322

Effectively, previously many queries were sent as `extended` even though at the driver side the query was like `send query with QUERY_EXECUTE_AS_SIMPLE flag`.
For instance, `connection.isValid()` was coded to use simple queries, and it was using extended in practice, thus it suffered from `prepared statement is not valid` kind of errors.

Good to know you are not using autosave though.