--
*From:* Mladen Marinović
*Sent:* Monday, May 5, 2025 12:27 PM
*To:* Achilleas Mantzios
*Cc:* pgsql-general@lists.postgresql.org
*Subject:* Re: Different execution plans in PG17 and
p
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 S
his bouncing layer.
From: Mladen Marinović
Sent: Monday, May 5, 2025 1:26 PM
To: Efrain J. Berdecia
Cc: SERHAD ERDEM ; Achilleas Mantzios
; pgsql-general@lists.postgresql.org
Subject: Re: Different execution plans in PG17 and pgBouncer...
Hi,
Mystery not solved...but identi
eries.
>
>
> I did that already. But the slow query is the consequence of the different
> plan, not the statistics.
>
>
> --
> *From:* Mladen Marinović
> *Sent:* Monday, May 5, 2025 12:27 PM
> *To:* Achilleas Mantzios
> *Cc:* pgsql-genera
ql-general@lists.postgresql.org
Subject: Re: Different execution plans in PG17 and pgBouncer...
On Mon, May 5, 2025 at 12:07 PM Achilleas Mantzios
wrote:
On 5/5/25 11:00, Mladen Marinović wrote:
On Mon, May 5, 2025 at 11:24 AM Achilleas Mantzios
wrote:
On 5/5/25 09:52, Mladen Marinović wro
: Monday, May 5, 2025 12:52 PM
To: SERHAD ERDEM
Cc: Achilleas Mantzios ;
pgsql-general@lists.postgresql.org
Subject: Re: Different execution plans in PG17 and pgBouncer...
On Mon, May 5, 2025 at 2:38 PM SERHAD ERDEM
mailto:serh...@hotmail.com>> wrote:
Hi , you had better try vacuum analy
tatistics.
> --
> *From:* Mladen Marinović
> *Sent:* Monday, May 5, 2025 12:27 PM
> *To:* Achilleas Mantzios
> *Cc:* pgsql-general@lists.postgresql.org <
> pgsql-general@lists.postgresql.org>
> *Subject:* Re: Different execution plans in PG17 and pgBouncer...
>
On Mon, May 5, 2025 at 2:36 PM Achilleas Mantzios <
a.mantz...@cloud.gatewaynet.com> wrote:
>
> On 5/5/25 13:27, Mladen Marinović wrote:
>
>
>
> On Mon, May 5, 2025 at 12:07 PM Achilleas Mantzios <
> a.mantz...@cloud.gatewaynet.com> wrote:
>
>>
>> On 5/5/25 11:00, Mladen Marinović wrote:
>>
>>
>>
execution plans in PG17 and pgBouncer...
On Mon, May 5, 2025 at 12:07 PM Achilleas Mantzios
mailto:a.mantz...@cloud.gatewaynet.com>> wrote:
On 5/5/25 11:00, Mladen Marinović wrote:
On Mon, May 5, 2025 at 11:24 AM Achilleas Mantzios
mailto:a.mantz...@cloud.gatewaynet.com>> wro
On 5/5/25 13:27, Mladen Marinović wrote:
On Mon, May 5, 2025 at 12:07 PM Achilleas Mantzios
wrote:
On 5/5/25 11:00, Mladen Marinović wrote:
On Mon, May 5, 2025 at 11:24 AM Achilleas Mantzios
wrote:
On 5/5/25 09:52, Mladen Marinović wrote:
Hi,
We
On 5/5/25 11:30, Ruben Morais wrote:
HI,
Could be a hint but test with jit to off.
If not wrong as you change from 11 to 17, that could be a cause, just
try it because in some cases plans changed when jit is on.
Not only JIT but also other extensions (such as timescale) could greatly
affect
On Mon, May 5, 2025 at 12:07 PM Achilleas Mantzios <
a.mantz...@cloud.gatewaynet.com> wrote:
>
> On 5/5/25 11:00, Mladen Marinović wrote:
>
>
>
> On Mon, May 5, 2025 at 11:24 AM Achilleas Mantzios <
> a.mantz...@cloud.gatewaynet.com> wrote:
>
>>
>> On 5/5/25 09:52, Mladen Marinović wrote:
>>
>> Hi
On 5/5/25 11:00, Mladen Marinović wrote:
On Mon, May 5, 2025 at 11:24 AM Achilleas Mantzios
wrote:
On 5/5/25 09:52, Mladen Marinović wrote:
Hi,
We recently migrated our production instances from PG11 to PG17.
While doing so we upgraded our pgBouncer instances from 1.12 t
On 5/5/25 09:52, Mladen Marinović wrote:
Hi,
We recently migrated our production instances from PG11 to PG17. While
doing so we upgraded our pgBouncer instances from 1.12 to 1.24. As
everything worked on the test servers we pushed this to production a
few weeks ago. We did not notice any pro
Hi,
We recently migrated our production instances from PG11 to PG17. While
doing so we upgraded our pgBouncer instances from 1.12 to 1.24. As
everything worked on the test servers we pushed this to production a few
weeks ago. We did not notice any problems until a few days ago (but the
problems we
15 matches
Mail list logo
