Re: Fix assert failure when decoding XLOG_PARAMETER_CHANGE on primary

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Fix assert failure when decoding XLOG_PARAMETER_CHANGE on primary
Дата
Msg-id CAA4eK1LQbm7JQA8feNoztDFccduFTVFs+51hm_U56tvunCAmOg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Fix assert failure when decoding XLOG_PARAMETER_CHANGE on primary  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Thu, Feb 6, 2025 at 12:30 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> I've updated the patch accordingly.
>

Today, again thinking about the proposed fix, I was wondering about
the following case. Say, on hot_standby, the user created a logical
slot, then shut down hot_standby, turn off the hot_standby flag, and
restart standby. This is allowed today but not after the patch. It is
possible that the user can promote a non-hot_standby server after its
restart in the previous step and can reuse the logical slot. So, is it
okay to change this behavior? If not, then we may need to go back to
the first fix proposed by you in this thread.

--
With Regards,
Amit Kapila.



В списке pgsql-hackers по дате отправления: