Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Дата
Msg-id CAA4eK1KkGJRYZKF5Tjp7fj7V4UiZDg6YY+WDK7fyjc14TW0duw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Dilip Kumar <dilipbalaut@gmail.com>)
Ответы Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Dilip Kumar <dilipbalaut@gmail.com>)
Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Дерево обсуждения 
On Wed, Oct 14, 2020 at 4:51 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Wed, Oct 14, 2020 at 4:12 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> >
> > Thanks for the tests. The latest patch looks mostly good to me. I have
> > made minor changes to the patch (a) changed the order where the new
> > message is placed at one place to make it consistent with other
> > places, (b) as discussed offlist, removed the extra increment to a
> > local variable in ReorderBufferRestoreChange, (c) ran pgindent.
> >
> > See the attached and let me know what do you think?
>
> The changes look good to me.
>

Pushed!

-- 
With Regards,
Amit Kapila.

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: pgsql: Restore replication protocol's duplicate command tags
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Add Information during standby recovery conflicts