| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables |
| Date: | 2020-10-15 07:08:49 |
| Message-ID: | CAA4eK1KkGJRYZKF5Tjp7fj7V4UiZDg6YY+WDK7fyjc14TW0duw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 14, 2020 at 4:51 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Wed, Oct 14, 2020 at 4:12 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2020-10-15 07:15:51 | Re: Add Information during standby recovery conflicts |
| Previous Message | Amit Kapila | 2020-10-15 07:07:04 | Re: pgsql: Restore replication protocol's duplicate command tags |