Feedback-ID: ie3de48e3:Fastmail
Date: Mon, 5 May 2025 16:08:03 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Mladen =?utf-8?Q?Marinovi=C4=87?= <marin@kset.org>
Cc: "Efrain J. Berdecia" <ejberdecia@yahoo.com>, 
	SERHAD ERDEM <serhade@hotmail.com>, Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: Different execution plans in PG17 and pgBouncer...
Message-ID: <202505051408.yhtnptcyduqf@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHjkqPQCmRwDMLSX2N_Gp+5WL+xJbtaoF2_aVCHxxQFPQApFxA@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202505051408.yhtnptcyduqf%40alvherre.pgsql>
Precedence: bulk

On 2025-May-05, Mladen Marinović wrote:

> Hi,
> 
> Mystery not solved...but identified. The pool is in transaction mode and
> some connections use set enable_mergejoin=off, but they do not set it back
> to on.

Maybe instead of "SET enable_mergejoin=off" these connections could be
changed to use SET LOCAL enable_mergejoin=off.  That way, the setting
reverts to its original value automatically at the end of the
transaction.  It seems more appropriate when using transaction mode
anyway.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/