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 | CAA4eK1J8kZzz31N=t5pgicWFKh3Hxddd+jQ3SZb3Z4K-8pXuEQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables (Andres Freund <andres@anarazel.de>) |
Список | pgsql-hackers |
On Fri, Oct 16, 2020 at 2:00 AM Andres Freund <andres@anarazel.de> wrote: > > On 2020-10-15 12:38:49 +0530, Amit Kapila wrote: > > 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! > > Awesome - it's great to see this problem finally addressed! > Thanks, I'm glad that you liked it. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: