Re: pg_replication_origin_drop API potential race condition

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: pg_replication_origin_drop API potential race condition
Дата
Msg-id CAA4eK1LSib5yTJsa6S_7B7Z-Fsp3wZoFjs+t-4QuBK86dxyYhA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_replication_origin_drop API potential race condition  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: pg_replication_origin_drop API potential race condition  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
On Tue, Feb 9, 2021 at 4:16 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2021-Feb-09, Amit Kapila wrote:
>
> > Now, we can do this optimization if we want but I am not sure if
> > origin_drop would be a frequent enough operation that we add such an
> > optimization. For now, I have added a note in the comments so that if
> > we find any such use case we can implement such optimization in the
> > future. What do you think?
>
> By all means let's get the bug fixed.
>

I am planning to push this in HEAD only as there is no user reported
problem and this is actually more about giving correct information to
the user rather than some misleading message. Do you see any need to
back-patch this change?

-- 
With Regards,
Amit Kapila.



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: libpq debug log
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Single transaction in the tablesync worker?