Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Date
Msg-id 20201015203026.6hi2ex4rmbvzssef@alap3.anarazel.de
Whole thread Raw
In response to Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
List pgsql-hackers
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!



pgsql-hackers by date:

Previous
From: Russell Foster
Date:
Subject: Re: [Patch] Using Windows groups for SSPI authentication
Next
From: Thomas Munro
Date:
Subject: Re: kevent latch paths don't handle postmaster death well