| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Mladen Marinović <marin(at)kset(dot)org> |
| Cc: | "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>, SERHAD ERDEM <serhade(at)hotmail(dot)com>, Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Different execution plans in PG17 and pgBouncer... |
| Date: | 2025-05-05 14:08:03 |
| Message-ID: | 202505051408.yhtnptcyduqf@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2025-05-05 14:09:01 | Re: Different execution plans in PG17 and pgBouncer... |
| Previous Message | SERHAD ERDEM | 2025-05-05 13:36:30 | Re: Different execution plans in PG17 and pgBouncer... |