Re: issue with synchronized_standby_slots

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
Cc: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: issue with synchronized_standby_slots
Date: 2025-10-23 04:06:07
Message-ID: CAA4eK1+-CkA62eeNVB3HH_Ss1JSOyFLmS+M93yWw6W+x8O91Ng@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 9, 2025 at 10:53 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Oct 8, 2025 at 9:05 PM Fabrice Chapuis <fabrice636861(at)gmail(dot)com> wrote:
> >
> > As Ashutosh suggests I will go more for the backpatching approach because the synchronized_standby_slots parameter impacts the last 2 major versions and this problem is critical on production environments.
> >
>
> Fair enough. Let's wait for the related issue being discussed in email
> [1] to be fixed.
>

As the other patch is committed
(f33e60a53a9ca89b5078df49416acae20affe1f5), can you update and prepare
backbranch patches for this fix as well?

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-10-23 04:08:22 Re: [PATCH] Free memory allocated by waitonlock_error_callback()
Previous Message Richard Guo 2025-10-23 03:43:36 Re: Issue with query_is_distinct_for() and grouping sets