Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
| От | Dilip Kumar |
|---|---|
| Тема | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables |
| Дата | |
| Msg-id | CAFiTN-sb8NEj+QSZF7TqySBhJww-a6HkC4YPtGCgQB3WYcT4Cg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
|
| Список | pgsql-hackers |
On Thu, Oct 15, 2020 at 12:38 PM Amit Kapila <amit.kapila16@gmail.com> 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! Thanks! -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: