Message-ID: <gh-pgjdbc-pgjdbc-3894-c3669257657@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 18 Dec 2025 09:14:56 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3894: Performance regression caused by keeping QUERY_EXECUTE_AS_SIMPLE flag
In-Reply-To: <gh-pgjdbc-pgjdbc-3894@github.com>
References: <gh-pgjdbc-pgjdbc-3894@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3669257657
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3894
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3894#issuecomment-3669257657
Content-Type: text/plain; charset=utf-8

@dreis2211 , there's an issue with just dropping "simple" flag from `BEGIN` statements as it might trigger a case like in https://github.com/pgjdbc/pgjdbc/issues/3107#issuecomment-3051715469

A trivial patch would probably be "refrain from execute as single when autosave=never", however, a proper fix would need more thought regarding "an extra sync message" or something like that.

> Do you want me to contribute the suggested changes?

I can cover the changes unless you are into analysis of how the flag plays with autosave and or issue #3107