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-09 05:23:54
Message-ID: CAA4eK1KUQhwCFnFGm3UpgoVpOTvAxo_80S68nsMUsjrST3aNnA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

[1] - https://www.postgresql.org/message-id/CAHGQGwFud-cvthCTfusBfKHBS6Jj6kdAPTdLWKvP2qjUX6L_wA%40mail.gmail.com

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-10-09 05:26:21 Re: Invalid primary_slot_name triggers warnings in all processes on reload
Previous Message Antonin Houska 2025-10-09 05:09:00 Re: Eager aggregation, take 3