Message-ID: <gh-pgjdbc-pgjdbc-3894-c3667418507@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 17 Dec 2025 22:14:49 +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: davecramer
X-GitHub-Comment-Id: 3667418507
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-3667418507
Content-Type: text/plain; charset=utf-8

> [@vlsi](https://github.com/vlsi) Do you want me to contribute the suggested changes?
> 
> Also - do you have an idea (or want to investigate) why running things with the `QUERY_EXECUTE_AS_SIMPLE` flag seems to be bad for performance?

Yes, to contributing changes. Execute as simple is allegedly bad form. We are not supposed to mix simple and extended, however it has worked forever