pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  
help / color / mirror / Atom feed
From: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3894: Performance regression caused by keeping QUERY_EXECUTE_AS_SIMPLE flag
Date: Thu, 18 Dec 2025 09:14:56 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

@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

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] issue #3894: Performance regression caused by keeping QUERY_EXECUTE_AS_SIMPLE flag
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox